| 2 | Approval of Agenda | |
|---|---|---|
| R1-2007500 | Draft Agenda of RAN1#103-e meeting | RAN1 Chair |
| R1-2009371 | Additional Guidelines for RAN1#103 e-Meeting Management | RAN1 Chair |
| R1-2009372 | RAN1#103-e Meeting Invitation, Timelines, Scope, Process | RAN1 Chair, ETSI MCC |
| 3 | Highlights from RAN plenary | |
| R1-2007502 | Highlights from RAN#89-e | RAN1 Chair |
| 4 | Approval of Minutes from previous meetings | |
| R1-2007501 | Report of RAN1#102-e meeting | ETSI MCC |
| 5 | Incoming Liaison Statements | |
| R1-2007503 | LS on definition of NR V2X con-current operation | RAN4, Huawei |
| R1-2007504 | LS on additional DC location reporting for intra-band UL CA | RAN4, Qualcomm |
| R1-2007505 | LS reply to RAN1 on UE capability on wideband carrier operation for NR-U | RAN4, MediaTek |
| R1-2007506 | LS on multiple BWP switch impact on HARQ design in dormancy SCell | RAN4, MediaTek |
| R1-2007507 | Reply LS on SCell Dormancy | RAN4, Huawei |
| R1-2007508 | Reply LS on UE capability xDD differentiation for SUL/SDL bands | RAN4, ZTE |
| R1-2007509 | Reply LS on power control for NR-DC | RAN4, vivo |
| R1-2007510 | LS on updated Rel-16 RAN4 UE features lists for NR and LTE | RAN4, CMCC |
| R1-2007511 | Reply LS on positioning SRS during DRX inactive time | RAN4, Apple |
| R1-2007512 | LS on number of configurable CSI-RS resources per MO | RAN4, Huawei |
| R1-2007513 | Full slot formats support in TDD UL-DL configuration | RAN3, Qualcomm |
| R1-2007514 | LS on new PQI support for PC5 communication | SA2, OPPO |
| R1-2007515 | LS on Direct Discovery and Relay in SA2 | SA2, OPPO |
| R1-2007516 | Reply LS to 5G-ACIA-LS-2020-WI042 = RP-201279 on 3GPP NR Rel-16 URLLC and IIoT performance evaluation | RAN, Ericsson |
| R1-2007517 | Reply LS on Rel-16 UE feature lists for NR DAPS | RAN2, Huawei |
| R1-2007518 | LS on Incomplete LTE Physical Layer Capabilities | RAN2, Huawei |
| R1-2007519 | LS to RAN1 on beamSwitchTiming | RAN2, vivo |
| R1-2007520 | LS on UE capability for V2X | RAN2, OPPO |
| R1-2007521 | LS on RAN2 agreements and RAN1 related issues | RAN2, LG Electronics |
| R1-2007522 | LS to RAN1 on sidelink configured grant handling | RAN2, Huawei |
| R1-2007523 | LS on Intra UE Prioritization Scenario | RAN2, Ericsson |
| R1-2007524 | LS on the error source for RAT-dependent positioning | RAN2, Huawei |
| R1-2007525 | LS on cell-grouping UE capability for synchronous NR-DC | RAN2, Qualcomm |
| R1-2007526 | LS on CAPC | RAN2, Nokia |
| R1-2007527 | Reply LS on exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI | RAN2, ZTE |
| R1-2007702 | Draft of LS response on URLLC Intra UE multiplexing | Ericsson |
| R1-2007724 | [DRAFT] Reply LS on Intra UE Prioritization Scenario | ZTE |
| R1-2007726 | [DRAFT] Reply LS on additional DC location reporting for intra-band UL CA | ZTE |
| R1-2007727 | Discussion on additional DC location reporting for intra-band UL CA | ZTE |
| R1-2007728 | [DRAFT] Reply LS on UE capability xDD differentiation for SULSDL bands | ZTE |
| R1-2007729 | Discussion on UE capability xDD differentiation for SULSDL bands | ZTE |
| R1-2007730 | [DRAFT] Reply LS on cell-grouping UE capability for synchronous NR-DC | ZTE |
| R1-2007731 | Discussion on cell-grouping UE capability for synchronous NR-DC | ZTE |
| R1-2007757 | Draft reply LS on beamSwitchTiming | ZTE |
| R1-2007795 | Discussion on additional DC location reporting for intra-band UL CA | CATT |
| R1-2007796 | Discussion on full slot formats support in TDD UL-DL configuration | CATT |
| R1-2007797 | Draft reply LS on intra UE prioritization scenario | CATT |
| R1-2007798 | Discussion of RAN4's LS on number of configurable CSI-RS resources per MO | CATT |
| R1-2007799 | Discussion on LS from RAN2 on RAN2 agreements and RAN1 related issue | CATT |
| R1-2007800 | Discussion on the LS from RAN2 on sidelink configured grant handling | CATT |
| R1-2007801 | Draft reply LS on beamSwitchTiming | CATT |
| R1-2007919 | [DRAFT] Reply LS on RAN2 agreements and RAN1 related issues | ZTE, Sanechips |
| R1-2007920 | [DRAFT] Reply LS to RAN1 on sidelink configured grant handling | ZTE, Sanechips |
| R1-2007932 | Discussion on LS on number of configurable CSI-RS resources per MO | Intel Corporation |
| R1-2007968 | Discussion on the LS on CAPC | ZTE, Sanechips |
| R1-2007969 | Draft reply LS on full slot formats support in TDD UL-DL configuration | ZTE |
| R1-2008040 | Discussion on RAN4 LS on UE capability on wideband carrier operation for NR-U | LG Electronics |
| R1-2008077 | Discussion on RAN2 LS on Intra UE Prioritization Scenario | LG Electronics |
| R1-2008116 | Draft reply LS on beamSwitchTiming | Samsung |
| R1-2008117 | Discussion on LS on Intra UE Prioritization Scenario | Samsung |
| R1-2008118 | Draft reply LS on Full slot formats support in TDD UL-DL configuration | Samsung |
| R1-2008119 | Draft reply LS on RAN2 agreements and RAN1 related issues | Samsung |
| R1-2008120 | Draft reply LS to RAN1 on sidelink configured grant handling | Samsung |
| R1-2008207 | [Draft] Reply LS on UE capability on wideband carrier operation for NR-U | Nokia, Nokia Shanghai Bell |
| R1-2008208 | LS on DCI-based multiple BWP switch simultaneously | Nokia, Nokia Shanghai Bell |
| R1-2008228 | Discussion on LS on beamSwitchTiming for AP CSI-RS | OPPO |
| R1-2008233 | Discussion on reply LS on new PQI support for PC5 communication | OPPO |
| R1-2008234 | Draft reply LS on UE capability for V2X | OPPO |
| R1-2008305 | Discussion of the LS on CAPC | Ericsson |
| R1-2008306 | [Draft] Reply LS on Intra UE Prioritization Scenario | Nokia |
| R1-2008342 | [DRAFT] Reply LS on Incomplete LTE Physical Layer Capabilities | Huawei |
| R1-2008402 | Discussions on full slot formats support in TDD UL-DL configuration | LG Electronics |
| R1-2008505 | Draft LS response on DCI-based multiple BWP switch simultaneously | MediaTek Inc. |
| R1-2008506 | Draft LS response on cell-grouping UE capability for synchronous NR-DC | MediaTek Inc. |
| R1-2008520 | [Draft] Reply LS on UE capability on wideband carrier operation for NR-U | MediaTek Inc. |
| R1-2008525 | Discussion on LS on intra-UE prioritization | Intel Corporation |
| R1-2008586 | Draft reply LS on full slot format support | Qualcomm Incorporated |
| R1-2008587 | Discussion on cell-grouping UE capabilities for synchronous NR-DC | Qualcomm Incorporated |
| R1-2008588 | Draft LS reply on cell-grouping UE capability for synchronous NR-DC | Qualcomm Incorporated |
| R1-2008589 | Draft reply LS on UE capability for V2X | Qualcomm Incorporated |
| R1-2008590 | Draft reply LS on RAN2 agreements and RAN1 related issues | Qualcomm Incorporated |
| R1-2008591 | Draft reply LS to RAN 2 LS on beamSwitchTiming | Qualcomm Incorporated |
| R1-2008592 | Draft reply LS to RAN 2 LS on intra-UE prioritization | Qualcomm Incorporated |
| R1-2008593 | Draft reply LS on LS to RAN1 on sidelink configured grant handling | Qualcomm Incorporated |
| R1-2008594 | Draft response LS to RAN4 on UE capability on wideband carrier operation for NR-U | Qualcomm Incorporated |
| R1-2008595 | Draft reply LS to RAN4 LS on additional DC location reporting for intra-band UL CA | Qualcomm Incorporated |
| R1-2008642 | Draft Reply LS on Intra UE Prioritization Scenario | vivo |
| R1-2008643 | Draft Reply LS on cell-grouping UE capability for synchronous NR-DC | vivo |
| R1-2008644 | Draft Reply LS on UE capability on wideband carrier operation for NR-U | vivo |
| R1-2008645 | Draft Reply LS on new PQI support for PC5 communication | vivo |
| R1-2008646 | Draft Reply LS on UE capability for V2X | vivo |
| R1-2008647 | Draft Reply LS on RAN2 agreements for V2X | vivo |
| R1-2008648 | Draft Reply LS on sidelink configured grant handling | vivo |
| R1-2008649 | Draft Reply LS on number of configurable CSI-RS resources per MO | vivo |
| R1-2008650 | Draft Reply LS on additional DC location reporting for intra-band UL CA | vivo |
| R1-2008651 | Draft Reply LS on beamSwitchTiming | vivo |
| R1-2008652 | Draft Reply LS on DCI-based multiple BWP switch simultaneously | vivo |
| R1-2008708 | On additional DC location reporting for intra-band UL CA | Nokia, Nokia Shanghai Bell |
| R1-2008734 | Maximum number of CSI-RS for L3 mobility | Nokia, Nokia Shanghai Bell |
| R1-2008735 | [DRAFT] Response LS on the number of configurable CSI-RS resources per MO | Nokia, Nokia Shanghai Bell |
| R1-2008744 | [Draft] LS on UE capability for V2X | Ericsson |
| R1-2008745 | [Draft] LS on new PQI values for PC5 communication | Ericsson |
| R1-2008746 | Discussion on RAN2 LS on SL CG handling | Ericsson |
| R1-2008747 | [Draft] LS reply on SL CG handling | Ericsson |
| R1-2008748 | Discussion on RAN2 LS on RAN2 agreements and RAN1 related issues | Ericsson |
| R1-2008749 | [Draft] LS reply on RAN2 agreements and RAN1 related issues | Ericsson |
| R1-2008773 | Draft reply on additional DC location reporting for intra-band UL CA | Huawei, HiSilicon |
| R1-2008774 | Discussion on additional DC location reporting for intra-band UL CA | Huawei, HiSilicon |
| R1-2008775 | On DCI-based multiple BWP switch simultaneously | Huawei, HiSilicon |
| R1-2008778 | Discussion on UE capability xDD differentiation for SUL/SDL bands | Huawei, HiSilicon |
| R1-2008780 | Discussion on UE capability on wideband carrier operation for NR-U | Huawei, HiSilicon |
| R1-2008781 | On sidelink configured grant handling | Huawei, HiSilicon |
| R1-2008782 | Sidelink configuration by NR Uu in PC5-only bands | Huawei, HiSilicon |
| R1-2008783 | On resource reselection due to dropped retransmissions | Huawei, HiSilicon |
| R1-2008784 | On definition of NR V2X con-current operation | Huawei, HiSilicon |
| R1-2008788 | On new PQI support for PC5 communication | Huawei, HiSilicon |
| R1-2008790 | DRAFT LS reply on UE capability on wideband carrier operation for NR-U | Huawei, HiSilicon |
| R1-2008791 | [Draft] Reply LS on beamSwitchTiming | Huawei, HiSilicon |
| R1-2008794 | Discussion on the LS on cell-grouping UE capability for synchronous NR-DC | Huawei, HiSilicon |
| R1-2008795 | Discussion on the LS on Full slot formats support in TDD UL-DL configuration | Huawei, HiSilicon |
| R1-2008866 | Discussion on LS on intra-UE prioritization | Intel Corporation |
| R1-2009067 | [Draft] Reply LS on Intra UE Prioritization Scenario | vivo |
| R1-2009232 | RAN1#103-e preparation phase on LSs | RAN1 Chair |
| R1-2009358 | LS on signalling of satellite backhaul connection | SA2, Samsung |
| R1-2009359 | LS on PC5 DRX operation | SA2, LG Electronics |
| R1-2009435 | Reply LS on Incomplete LTE Physical Layer Capabilities | RAN1, Huawei |
| R1-2009489 | Reply LS on maximum data rate for NR sidelink | RAN2, OPPO |
| R1-2009491 | Reply LS on definition of NR V2X con-current operation | RAN1, Huawei |
| R1-2009505 | Reply LS on full slot formats support in TDD UL-DL | RAN1, Qualcomm Incorporated |
| R1-2009508 | LS on RAN1 agreement on pre-emption | RAN2, LG Electronics |
| R1-2009575 | Reply LS on DCI-based multiple BWP switch simultaneously | RAN1, MediaTek |
| R1-2009576 | Reply LS on UE capability xDD differentiation for SUL/SDL bands | RAN1, Samsung |
| R1-2009591 | Summary of [103-e-AI5-LS-06] Email discussion/approval of a potential reply LS in response to R1-2005208 | Moderator (Samsung) |
| R1-2009605 | Reply LS on Latency of NR Positioning Protocols | RAN2, Intel |
| R1-2009621 | Reply LS on new PQI support for PC5 communication | RAN1, OPPO |
| R1-2009622 | Summary of LS discussion on new PQI support for PC5 | Moderator (OPPO) |
| R1-2009644 | LS on per-table MCS range for mode-2 | RAN2, OPPO |
| R1-2009645 | Reply LS on definition of NR V2X con-current operation | RAN2, Huawei |
| R1-2009669 | Reply LS on updated Rel-16 LTE and NR parameter lists | RAN2, Ericsson |
| R1-2009714 | Reply LS on updated Rel-16 LTE parameter lists | RAN2, Samsung |
| R1-2009758 | LS on Rel-16 updated RAN4 UE features lists for LTE and NR | RAN4, CMCC |
| 5.1 | RAN1 Aspects for RF requirements for NR frequency range 1 (FR1) | |
| R1-2007603 | Discussion on the remaining problems of supporting Tx switching between two uplink carriers | Huawei, HiSilicon |
| R1-2007725 | Remaining Maintenance Issues of UL Tx Switching | ZTE |
| R1-2008229 | Text Proposals for Tx Switching between Two Uplink Carriers | OPPO |
| R1-2008564 | Draft CR to 38.213 on corrections for UL Tx switching | Ericsson |
| R1-2008596 | Remaining issues for 1Tx-2Tx switching | Qualcomm Incorporated |
| R1-2008814 | Summary of uplink Tx switching | Moderator (China Telecom) |
| R1-2009587 | Correction on uplink Tx switching | Moderator (China Telecom) |
| R1-2009590 | Draft LS on uplink Tx switching | China Telecom |
| R1-2009676 | LS on uplink Tx switching | RAN1, China Telecom |
| R1-2009690 | Summary of [103-e-NR-LS-TxSwitching-01] on maintenance of uplink Tx switching | Moderator (China Telecom) |
| R1-2009691 | Summary of [103-e-NR-LS-TxSwitching-02] on maintenance of uplink Tx switching | Moderator (China Telecom) |
| 5.2 | RAN1 Aspects for RF Requirement Enhancements for FR2 | |
| R1-2007747 | Enhancement on FR2 MPE mitigation | ZTE |
| 6.1 | Maintenance of E-UTRA Releases 8–15 | |
| R1-2008338 | Corrections on preamble format indicator presence in NPDCCH order in TS 36.212 | Huawei, HiSilicon |
| R1-2008339 | Corrections on preamble format indicator presence in NPDCCH order in TS 36.213 | Huawei, HiSilicon |
| R1-2008341 | Corrections on interference randomization for NB-IoT SPS | Huawei, HiSilicon, MediaTek, Qualcomm |
| R1-2008582 | Clarification on the subcarrier allocation for sub-PRB in CE Mode B | Ericsson |
| R1-2009228 | RAN1#103-e preparation phase on Maintenance of E-UTRA Releases 8-15 | Ad-Hoc Chair (Ericsson) |
| R1-2009424 | Corrections on interference randomization for NB-IoT SPS | Huawei, HiSilicon, MediaTek, Qualcomm |
| R1-2009425 | Corrections on interference randomization for NB-IoT SPS | Huawei, HiSilicon, MediaTek, Qualcomm |
| R1-2009436 | Clarification on the subcarrier allocation for sub-PRB in CE Mode B | Ericsson |
| R1-2009437 | Clarification on the subcarrier allocation for sub-PRB in CE Mode B | Ericsson |
| R1-2009438 | Corrections on preamble format indicator presence in NPDCCH order in TS 36.212 | Huawei, HiSilicon |
| R1-2009439 | Corrections on preamble format indicator presence in NPDCCH order in TS 36.212 | Huawei, HiSilicon |
| R1-2009440 | Corrections on preamble format indicator presence in NPDCCH order in TS 36.213 | Huawei, HiSilicon |
| R1-2009441 | Corrections on preamble format indicator presence in NPDCCH order in TS 36.213 | Huawei, HiSilicon |
| R1-2009563 | Summary on [103-e-LTE-6.1CRs-01] on preamble format indicator presence in NPDCCH order | Moderator(Huawei) |
| R1-2009564 | Summary on [103-e-LTE-6.1CRs-02] on interference randomization for NB-IoT SPS | Moderator(Huawei) |
| R1-2009819 | Session notes for 6.1 (Maintenance of E-UTRA Releases 8-15) | Ad-Hoc Chair (Ericsson) |
| 6.2 | Maintenance of E-UTRA Release 16 | |
| R1-2008793 | Alignment corrections for Rel-16 features | FUTUREWEI |
| R1-2009538 | Alignment corrections for Rel-16 features | FUTUREWEI |
| R1-2009764 | Alignment of terminology for Rel-16 Additional MTC Enhancements for LTE | Lenovo, Motorola Mobility |
| R1-2009785 | Alignment corrections for Rel-16 features | Ericsson |
| R1-2009820 | Session notes for 6.2.1 (Maintenance of Additional MTC Enhancements) and 6.2.2 (Maintenance of Additional Enhancements for NB-IoT) | Ad-hoc Chair (Samsung) |
| 6.2.1 | Maintenance of Additional MTC Enhancements | |
| R1-2007713 | Remaining issues on scheduling enhancement for MTC | ZTE |
| R1-2008340 | Corrections on multi-TB scheduling for eMTC | Huawei, HiSilicon |
| R1-2008522 | Maintenance on multi-TB scheduling | Qualcomm Incorporated |
| R1-2008583 | PUR maintenance issues for Rel-16 LTE-MTC | Ericsson |
| R1-2008692 | Multi-TB and resource reservation maintenance issues for Rel-16 LTE-MTC | Ericsson |
| R1-2008800 | Corrections on transmission modes for PUR | Huawei, HiSilicon |
| R1-2009295 | FL summary for Multi-TB issues for Rel-16 LTE-MTC | Moderator (Ericsson) |
| R1-2009296 | FL summary for parameter name corrections for Rel-16 LTE-MTC | Moderator (Ericsson) |
| R1-2009442 | FL summary for PUR email [103-e-LTE-eMTC5-01] | Moderator (Sierra Wireless) |
| R1-2009443 | PUR configuration of transmission mode | Moderator (Sierra Wireless), Ericsson, Huawei, HiSilicon, Qualcomm, Lenovo, Motorola Mobility |
| R1-2009612 | Corrections for multi-TB early termination | Moderator (Ericsson), Qualcomm Incorporated, ZTE, Ericsson, Lenovo, Motorola Mobility |
| R1-2009613 | Correction on explicit feedback for multi-TB scheduling in LTE-MTC | Moderator (Ericsson), ZTE, Ericsson, Qualcomm, Lenovo |
| R1-2009614 | Correction on TPC command for multi-TB scheduling in LTE-MTC | Moderator (Ericsson), ZTE, Ericsson, Qualcomm, Lenovo |
| R1-2009725 | Text proposals on explicit feedback for MTB | ZTE |
| R1-2009726 | TP for Support of implicit HARQ-ACK feedback | Qualcomm Incorporated |
| R1-2009840 | Corrections for multi-TB early termination | Moderator (Ericsson), Qualcomm Incorporated, ZTE, Ericsson, Lenovo, Motorola Mobility |
| 6.2.2 | Maintenance of Additional Enhancements for NB-IoT | |
| R1-2007712 | Correction on L1 adjustment on PUR repetition number | ZTE |
| R1-2007714 | Clarifications on scheduling enhancement for NB-IoT | ZTE |
| R1-2008584 | PUR maintenance issues for Rel-16 NB-IoT | Ericsson |
| R1-2008797 | Corrections on transmission in preconfigured UL resources | Huawei, HiSilicon |
| R1-2009466 | Summary of email discussion [103-e-LTE-NB_IoTenh3-03] | Moderator (ZTE) |
| R1-2009467 | Correction on HARQ process ID assumption for multi-TB | Moderator (ZTE) |
| R1-2009468 | Clarification on usage of NDI | Moderator (ZTE) |
| R1-2009618 | Corrections on UE-specific search space by PUR-RNTI | Moderator (Huawei), Huawei, HiSilicon, Ericsson |
| R1-2009619 | Corrections on the NPUSCH repetition adjustment field | Moderator (Huawei), Huawei, HiSilicon, Ericsson, ZTE |
| R1-2009620 | Corrections on PUR-RNTI for NB-IoT | Moderator (Huawei), Huawei, HiSilicon, Ericsson |
| R1-2009704 | Feature lead summary #1 on [103-e-LTE-NB_IoTenh3-01] | Moderator (Huawei) |
| R1-2009705 | Text Proposal for Issue#1 in [103-e-LTE-NB_IoTenh3-01] | Moderator (Huawei) |
| R1-2009706 | Feature lead summary #1 on [103-e-LTE-NB_IoTenh3-02] | Moderator (Huawei) |
| 6.2.3 | Maintenance of DL MIMO efficiency enhancements for LTE | |
| R1-2008798 | Corrections on additional SRS symbols | Huawei, HiSilicon |
| R1-2009426 | Corrections on additional SRS symbols | Huawei, HiSilicon |
| R1-2009427 | Corrections on additional SRS symbols | Huawei, HiSilicon |
| R1-2009565 | Summary on [103-e-LTE-LTE_DL_MIMO_EE-01] on additional SRS symbols | Moderator(Huawei) |
| R1-2009821 | Session notes for 6.2.3 (Maintenance of DL MIMO efficiency enhancements for LTE) | Ad-hoc Chair (Samsung) |
| 6.2.4 | Maintenance of LTE-based 5G Terrestrial Broadcast | |
| R1-2007740 | Draft 36.211 CR on LTE-based 5G Terrestrial Broadcast | ZTE |
| R1-2008523 | Correction for 0.37kHz SCS | Qualcomm Incorporated |
| R1-2009422 | CR on LTE-based 5G Terrestrial Broadcast | ZTE |
| R1-2009423 | Correction for 0.37kHz SCS | Qualcomm Incorporated |
| R1-2009822 | Session notes for 6.2.4 (Maintenance of LTE-based 5G Terrestrial Broadcast) | Ad-Hoc Chair (Ericsson) |
| 6.2.5 | LTE Rel-16 UE Features | |
| R1-2007912 | Summary of Other UE features for LTE | Moderator (AT&T) |
| R1-2008235 | Discussion on LTE Rel-16 UE features | OPPO |
| R1-2009350 | Updated RAN1 UE features list for Rel-16 LTE | Moderators (AT&T, NTT DOCOMO) |
| R1-2009351 | LS on updated Rel-16 RAN1 UE features lists for LTE | RAN1, AT&T, NTT DOCOMO |
| 6.2.6 | Other | |
| R1-2008524 | Power control for DAPS | Qualcomm Incorporated |
| R1-2008799 | Draft CR on power sharing for LTE DAPS | Huawei, HiSilicon |
| R1-2009229 | RAN1#103-e preparation phase on AI 6.2.6 Maintenance of E-UTRA Release 16 | Ad-Hoc Chair (Ericsson) |
| R1-2009528 | Power sharing for LTE DAPS | Moderator (Qualcomm Incorporated), Huawei |
| R1-2009533 | Summary of email discussion [103-e-LTE-6.6CRs] | Moderator (Qualcomm Incorporated) |
| R1-2009823 | Session notes for 6.2.6 (Maintenance of E-UTRA Release 16 Other) | Ad-Hoc Chair (Ericsson) |
| 7.1 | Maintenance of Release 15 NR | |
| R1-2007624 | 38.212CRdraft (Rel-16,F) RRC IE name fix to dynamic frequency domain resource allocation type selection (Rel-15 origin) | Nokia, Nokia Shanghai Bell |
| R1-2007722 | Discussion on Ambiguity Issues for UE Features with Cross-Carrier Operation | ZTE |
| R1-2007723 | Draft 38.213 CR on HARQ-ACK Determination for SPS Release | ZTE |
| R1-2007758 | Discussion on determining PHR for PUSCH in CA | ZTE |
| R1-2007759 | Draft CR on determining PHR for PUSCH in CA | ZTE |
| R1-2007760 | Discussion on closed-loop power control with an absolute TPC command | ZTE |
| R1-2007761 | Draft CR on closed-loop power control with an absolute TPC command | ZTE |
| R1-2007762 | Draft CR on power offset between SSB and CSI-RS | ZTE |
| R1-2007802 | Correction for UCI on Msg3 PUSCH and MsgA PUSCH | CATT |
| R1-2007803 | Correction for type1 HARQ-ACK codebook | CATT |
| R1-2007804 | Correction on HARQ-ACK generation for DL transmission with single TB when multi-TB is configured | CATT |
| R1-2007805 | Correction on UE sounding procedure | CATT |
| R1-2008121 | Draft CR on configured grant based PUSCH | Samsung |
| R1-2008122 | 38.211 DRAFT CR (Rel-16, F) on k_SSB calculation | Samsung |
| R1-2008123 | Draft CR for 38.211 for UE receiver behavior for a RS and its QCL reference | Samsung |
| R1-2008423 | Clarification of FG3-5b with Cross Carrier Operation | Apple |
| R1-2008424 | Discussion on PMI/RI restrictions for Type I Single Panel Codebook with 2 Tx | Apple |
| R1-2008425 | Draft CR on PMI/RI restrictions for Type I Single Panel Codebook with 2 Tx | Apple |
| R1-2008426 | Discussions on PUSCH skipping | Apple |
| R1-2008507 | Clarification on Numerology for Active DL and UL BWPs | MediaTek Inc. |
| R1-2008526 | Rel-15 CR on uplink transmission combination with PUCCH | NTT DOCOMO, INC. |
| R1-2008527 | Rel-16 CR on uplink transmission combination with PUCCH | NTT DOCOMO, INC. |
| R1-2008528 | Discussion on CG skipping vs UCI multiplexing on CG PUSCH | NTT DOCOMO, INC. |
| R1-2008597 | Draft CR on NNZC indicator of Rel-15 Type II CSI codebook | Qualcomm Incorporated |
| R1-2008598 | Discussion on CSI-RS ambiguities | Qualcomm Incorporated |
| R1-2008599 | Discussion on SRS carrier switching | Qualcomm Incorporated |
| R1-2008653 | Discussion on UE FG in case of cross-carrier operation | vivo |
| R1-2008654 | Disucssion on configured grant PUSCH with overlapping UCI on PUCCH in Rel-16 | vivo |
| R1-2008655 | Correction on 38.214 for PUSCH with UL skipping in Rel-16 | vivo |
| R1-2008656 | Draft CR on correction for Msg3 retransmission power control | vivo |
| R1-2008657 | Corrections on aperiodic SRS triggering minimal time interval | vivo, Nokia, Nokia Shanghai Bell |
| R1-2008658 | Discussion on aperiodic SRS triggering minimal time interval and zero slot offset | vivo |
| R1-2008659 | Correction on beamswitch timing for aperiodic TRS | vivo |
| R1-2008683 | Draft 38.214 CR (Rel-16, F, Rel-15 originating) to fix configurable xOverhead values for TBS determination | Nokia, Nokia Shanghai Bell |
| R1-2008767 | Clarification on the PUSCH scheduling constraint in Rel-15 | Apple |
| R1-2008776 | Discussion on UL skipping for CG PUSCH | Huawei, HiSilicon |
| R1-2008777 | Correction on supplementary uplink in 38.213 | Huawei, HiSilicon |
| R1-2008786 | Corrections on radio link monitoring in 38.213 in Rel-15 | Huawei, HiSilicon |
| R1-2008787 | Clarifications on UE features in case of cross-carrier operation | Huawei, HiSilicon |
| R1-2008839 | RAN1#103-e preparation phase initial summary on NR Rel-15 CRs | Ad-hoc chair (Samsung) |
| R1-2008840 | RAN1#103-e preparation phase final summary on NR Rel-15 CRs | Ad-hoc chair (Samsung) |
| R1-2009382 | CR on HARQ-ACK Determination for SPS Release | ZTE |
| R1-2009383 | CR on HARQ-ACK Determination for SPS Release | ZTE |
| R1-2009453 | RRC IE name fix to dynamic frequency domain resource allocation type selection (Rel-15 origin) | Moderator (Nokia) |
| R1-2009454 | 38.214 CR (Rel-16, F, Rel-15 originating) to fix configurable xOverhead values for TBS determination | Moderator (Nokia) |
| R1-2009484 | Summary for [103-e-NR-7.1CRs-07] 38.211 DRAFT CR (Rel-16, F) on k_SSB calculation | Moderator (Samsung) |
| R1-2009536 | Correction on HARQ-ACK generation for DL transmission with single TB when multi-TB is configured | CATT |
| R1-2009537 | Correction on HARQ-ACK generation for DL transmission with single TB when multi-TB is configured | CATT |
| R1-2009623 | LS on Interpretation of UE Features in Case of Cross-Carrier Operation | RAN1, ZTE |
| R1-2009624 | Summary of Email Discussion [103-e-NR-7.1CRs-01] | Moderator (ZTE) |
| R1-2009625 | Correction on supplementary uplink in 38.213 | Huawei, HiSilicon |
| R1-2009687 | Correction on 38.214 for PUSCH with UL skipping | Moderator (vivo) |
| R1-2009772 | LS on PUSCH skipping with UCI in Rel-16 | RAN1, vivo |
| R1-2009773 | Summary of email discussion [103-e-NR-7.1CRs-08]-phase 1 | Moderator (vivo) |
| R1-2009774 | Summary of email discussion [103-e-NR-7.1CRs-08]-phase 2 | Moderator (vivo) |
| R1-2009824 | Session notes for 7.1 (Maintenance of Release 15 NR) | Ad-hoc Chair (Samsung) |
| 7.2 | Maintenance of Release 16 NR | |
| R1-2007794 | Alignment of RRC parameter names | Ericsson |
| R1-2008124 | Alignment CR for TS 38.213 | Samsung |
| R1-2008202 | Alignment of RRC parameter names | Intel Corporation (UK) Ltd |
| R1-2008292 | Alignment of RRC parameter names for 38.214 | Nokia, Nokia Shanghai Bell |
| R1-2008792 | Alignment of RRC parameter names for TS 38.212 | Huawei |
| R1-2009742 | Alignment CR for TS 38.213 | Samsung |
| R1-2009751 | Alignment CR for TS 38.211 | Ericsson |
| R1-2009776 | Alignment of RRC parameter names for TS 38.212 | Huawei |
| R1-2009777 | Alignment of RRC parameter names | Intel Corporation (UK) Ltd |
| R1-2009778 | Alignment of RRC parameter names for 38.214 | Nokia, Nokia Shanghai Bell |
| 7.2.1 | Maintenance of Two step RACH for NR | |
| R1-2007963 | Text proposal on the MsgA configuration in unlicensed band | ZTE, Sanechips |
| R1-2007964 | FL summary on the maintenance of Rel-16 2-step RACH | Moderator (ZTE) |
| R1-2008418 | Maintenance of Two step RACH | Ericsson |
| R1-2008660 | Miscellaneous corrections for 2-step RACH | vivo |
| R1-2008785 | Remaining issues for 2-step RACH | Huawei, HiSilicon |
| R1-2009386 | Summary of email discussion [103-e-NR-2Step-01] | Moderator (ZTE) |
| R1-2009387 | Draft CR on HARQ Feedback Timing Indicator in 38.213 | Moderator (ZTE) |
| R1-2009388 | Draft CR on the determination of DMRS sequences in 38.211 | Moderator (ZTE) |
| R1-2009389 | Draft CR on validation rule of PUSCH occasions in 38.213 | Moderator (ZTE) |
| R1-2009445 | CR on the determination of DMRS sequences in 38.211 | Moderator (ZTE) |
| R1-2009446 | CR on 2-step RACH for 38.213 | Moderator (ZTE) |
| 7.2.2 | Maintenance of NR-based Access to Unlicensed Spectrum | |
| R1-2007606 | Maintenance on initial access signals and channels | Huawei, HiSilicon |
| R1-2007607 | Maintenance on DL signals and channels | Huawei, HiSilicon |
| R1-2007608 | Maintenance on channel access procedures | Huawei, HiSilicon |
| R1-2007609 | Maintenance on HARQ-ACK enhancement | Huawei, HiSilicon |
| R1-2007777 | Clarification on restriction of initial BWP configuration | Fujitsu |
| R1-2007778 | Clarification on resource allocation for PUSCH scheduled by RAR UL grant or DCI addressed to TC-RNTI | Fujitsu |
| R1-2007903 | Remaining Issues and Corrections on Channel Access Procedures and Configured Grants for NR-U | Nokia, Nokia Shanghai Bell |
| R1-2007933 | Remaining issues on NR-U | Intel Corporation |
| R1-2007959 | Text proposals on the initial access for NR-U | ZTE, Sanechips |
| R1-2007960 | Text proposal on the channel measurement and interference measurement | ZTE, Sanechips |
| R1-2007961 | Text proposals on type-3 HARQ-ACK codebook and multi-PUSCH scheduling | ZTE, Sanechips |
| R1-2007962 | Remaining issues on the configured grant for NR-U | ZTE, Sanechips |
| R1-2007978 | Initial Access Signals and Channels | Ericsson |
| R1-2007979 | DL Signals and Channels | Ericsson |
| R1-2007980 | Channel Access Procedures | Ericsson |
| R1-2007981 | HARQ Corrections | Ericsson |
| R1-2007985 | Remaining issues on UL transmissions | ETRI |
| R1-2008041 | Remaining issues of DL signals and channels for NR-U | LG Electronics |
| R1-2008042 | Remaining issues of random access for NR-U | LG Electronics |
| R1-2008043 | Remaining issues of channel access procedure and configured grant for NR-U | LG Electronics |
| R1-2008044 | Remaining issues of HARQ procedure for NR-U | LG Electronics |
| R1-2008125 | Remaining issues on Initial access signals and channels | Samsung |
| R1-2008126 | Remaining issues on DL signals and channels | Samsung |
| R1-2008127 | Remaining issues on channel access | Samsung |
| R1-2008128 | Remaining issues on HARQ | Samsung |
| R1-2008204 | Remaining issues on DL signals and channels | Nokia, Nokia Shanghai Bell |
| R1-2008205 | Remaining issues on Wideband operation in NR-U | Nokia, Nokia Shanghai Bell |
| R1-2008206 | Remaining issues on NR-U HARQ and Initial Access Procedures | Nokia, Nokia Shanghai Bell |
| R1-2008246 | Discussion on the remaining issues of initial access signal/channel | OPPO |
| R1-2008247 | Discussion on the remaining issues of DL signals and channels | OPPO |
| R1-2008248 | Discussion on the remaining issues of channel access procedure | OPPO |
| R1-2008249 | Discussion on the remaining issues of HARQ enhancements | OPPO |
| R1-2008383 | Remaining issues on channel access procedure for NR-U | Sharp |
| R1-2008384 | Remaining issues on DL signals/channels for NR-U | Sharp |
| R1-2008385 | Remaining issues on initial access and UL signals/channels for NR-U | Sharp |
| R1-2008386 | Remaining corrections for wideband operation for NR-U | Sharp |
| R1-2008521 | Correction on SRS position | CATT |
| R1-2008600 | PO configuration for 2-step RACH over multiple RB sets | Qualcomm Incorporated |
| R1-2008601 | TP for Channel access procedures for NR unlicensed | Qualcomm Incorporated |
| R1-2008602 | TP for DL signals and channels for NR-U | Qualcomm Incorporated |
| R1-2008603 | TP for Wideband operation for NR-U Operation | Qualcomm Incorporated |
| R1-2008632 | Remaining issues for DFI in NR-U | ASUSTeK |
| R1-2008661 | Remaining issues on HARQ operation for NR-U | vivo |
| R1-2008662 | Remaining issues on CG-PUSCH | vivo |
| R1-2008663 | TPs on HARQ feedback in CG-DFI for CBG-based PUSCH transmission | vivo |
| R1-2008664 | TPs on DL signals and channels | vivo |
| R1-2008693 | Feature lead summary for NR-U DL Signals and Channels | Moderator (Lenovo) |
| R1-2008724 | Correction on UL channel access procedure for NR-U | WILUS Inc. |
| R1-2008768 | Feature lead summary of NR-U enhancements to initial access procedures | Moderator (Charter Communications) |
| R1-2008801 | Feature Lead Summary on Channel Access Procedures for NR-U | Moderator (Nokia) |
| R1-2008845 | Summary on remaining issues of wide-band operation for NR-U | Moderator (LG Electronics) |
| R1-2008886 | Feature lead summary#1 on NR-U HARQ maintenance | Moderator (Huawei) |
| R1-2008887 | FL summary for initial access signals and channels for NR-U | Moderator (Qualcomm) |
| R1-2008888 | Summary of preparation phase email discussion for NR-U maintenance | Moderator (Qualcomm) |
| R1-2009080 | Feature lead summary on NRU configured grant enhancement | Moderator (vivo) |
| R1-2009227 | Feature lead summary for UL Signals and Channels | Moderator (Ericsson) |
| R1-2009357 | FL Summary #1 for [103-e-NR-NRU-03] Email discussion/approval | Moderator (Ericsson) |
| R1-2009409 | Summary of email discussion 01 for NR-U | Moderator (Qualcomm) |
| R1-2009410 | Email discussion summary for 103-e-NR-NRU-07 | Moderator (Qualcomm) |
| R1-2009413 | Summary of [103-e-NR-NRU-06] email discussion | Moderator (vivo) |
| R1-2009429 | Summary of [103-e-NR-NRU-02] email discussion | Moderator (Lenovo) |
| R1-2009549 | Correction to UE assumption on RB set configuration for PRACH | Moderator (Ericsson), LG Electronics, Sharp |
| R1-2009550 | Miscellaneous corrections on NR unlicensed configured grant | Moderator (vivo), ASUSTeK, Intel, Huawei, HiSilicon |
| R1-2009595 | Feature lead summary#1 for NRU HARQ [103-e-NR-NRU-05] | Moderator (Huawei) |
| R1-2009596 | Correction of NRU HARQ procedure in the presence of SPS PDSCH | Moderator (Huawei) |
| R1-2009611 | Correction of NRU HARQ procedure in the presence of SPS PDSCH | Moderator (Huawei) |
| R1-2009627 | CR to 38.211 on NR-U PRACH RO configuration | Moderator (Qualcomm) |
| R1-2009628 | CR to 38.213 on NR-U 2-step RACH PO configuration | Moderator (Qualcomm) |
| R1-2009689 | Reply LS on Clarification of UE behavior after receiving the MAC CE deactivation command for semi-persistent CSI reporting in NR-U | RAN1, Lenovo |
| R1-2009698 | CR to 37.213 to correct CP extension and LBT type for SRS | Moderator (Nokia), Samsung, Huawei, Broadcom, Ericsson, LGE |
| R1-2009699 | CR to 37.213 CR to correct CAPC for RACH | Moderator (Nokia), Samsung |
| R1-2009700 | CR to 37.213 to correct channel access for SRS | Moderator (Nokia), ETRI |
| R1-2009701 | CR to 38.211 to correct CP extension for SRS | Moderator (Nokia), Samsung |
| R1-2009702 | CR to 38.213 to correct references to 38.212 for RACH procedure | Moderator (Nokia), Ericsson |
| R1-2009703 | Correction on remaining channel occupancy assumption | Moderator (Lenovo) |
| R1-2009752 | Feature Lead Summary of emails discussion [103-e-NR-NRU-04] | Moderator (Nokia) |
| R1-2009825 | Session notes for 7.2.2 (Maintenance of NR-based Access to Unlicensed Spectrum) | Ad-Hoc Chair (Ericsson) |
| 7.2.3 | Maintenance of Integrated Access and Backhaul for NR | |
| R1-2008328 | Corrections on PDCCH monitoring of DCI format 2_5 | Huawei, HiSilicon |
| R1-2008409 | Correction on PDCCH monitoring for IAB-MT | LG Electronics |
| R1-2008707 | Corrections for Rel-16 IAB | Ericsson |
| R1-2008742 | Maintenance for Rel-16 IAB | Nokia, Nokia Shanghai Bell |
| R1-2009432 | Clarify DCI Format 2_5 search space sets | Moderator (AT&T) |
| R1-2009826 | Session notes for 7.2.3 (Maintenance of Integrated Access and Backhaul for NR) | Ad-hoc Chair (Samsung) |
| 7.2.4 | Maintenance for 5G V2X with NR sidelink | |
| R1-2007610 | Correction on sidelink PT-RS sequence generation | Huawei, HiSilicon |
| R1-2007611 | Remaining details of sidelink resource allocation mode 1 | Huawei, HiSilicon |
| R1-2007612 | Remaining details of sidelink resource allocation mode 2 | Huawei, HiSilicon |
| R1-2007613 | Remaining details of physical layer procedures for sidelink | Huawei, HiSilicon |
| R1-2007772 | Discussion on essential corrections in physical layer structure | LG Electronics |
| R1-2007773 | Discussion on essential corrections in resource allocation for Mode 1 | LG Electronics |
| R1-2007774 | Discussion on essential corrections in resource allocation for Mode 2 | LG Electronics |
| R1-2007775 | Discussion on essential corrections in sidelink synchronization mechanism | LG Electronics |
| R1-2007776 | Discussion on essential corrections in physical layer procedure | LG Electronics |
| R1-2007779 | A remaining issue on UE procedures for reporting HARQ-ACK on uplink | Fujitsu |
| R1-2007780 | A remaining issue on simultaneous transmissions of uplink and PUSCH carrying sidelink HARQ-ACK | Fujitsu |
| R1-2007809 | Remaining issues on physical layer structure for NR sidelink | CATT |
| R1-2007810 | Remaining issues on Mode 1 resource allocation in NR V2X | CATT |
| R1-2007811 | Remaining issues on Mode 2 resource allocation in NR V2X | CATT |
| R1-2007812 | Remaining issues on sidelink synchronization mechanism in NR V2X | CATT |
| R1-2007813 | Remaining issues on physical layer procedures for NR V2X | CATT |
| R1-2007921 | Remaining issues of NR sidelink physical layer structure | ZTE, Sanechips |
| R1-2007922 | Remaining issues in Mode-1 | ZTE, Sanechips |
| R1-2007923 | Remaining issues in mode 2 | ZTE, Sanechips |
| R1-2007924 | Remaining issues of synchronization | ZTE, Sanechips |
| R1-2007925 | Remaining issues in PHY procedures for Rel-16 sidelink | ZTE, Sanechips |
| R1-2007934 | Remaining opens of sidelink physical structure for NR V2X design | Intel Corporation |
| R1-2007935 | Corrections related to Mode-2 resource allocation | Intel Corporation |
| R1-2007936 | Corrections related to Mode-1 resource allocation | Intel Corporation |
| R1-2007986 | Remaining issues on resource allocation mode 2 for NR V2X | ETRI |
| R1-2007987 | Physical layer procedures for sidelink | ETRI |
| R1-2008081 | Maintenance for mode 2 resource allocation | NEC |
| R1-2008095 | Remaining issues in NR sidelink mode 1 resource allocation | Spreadtrum Communications |
| R1-2008096 | Remaining issues in NR sidelink mode 2 resource allocation | Spreadtrum Communications |
| R1-2008097 | Remaining issues on sidelink physical layer procedure | Spreadtrum Communications |
| R1-2008129 | Text Proposals on Physical Layer Structures for NR Sidelink | Samsung |
| R1-2008130 | Draft CR on PUCCH Power Control for NR Sidelink Mode 1 Scheduling | Samsung |
| R1-2008131 | Draft CR on Mode 2 for NR Sidelink | Samsung |
| R1-2008132 | Draft CR on Sidelink Physical Duration to Logical Slot Conversion | Samsung |
| R1-2008133 | Draft CR on Physical Layer Procedures for NR Sidelink | Samsung |
| R1-2008134 | Feature lead summary#1 for Physical layer structure for sidelink | Moderator (Samsung) |
| R1-2008230 | Draft TP on physical structure for NR sidelink | OPPO |
| R1-2008231 | Text proposal of mode 1 for NR sidelink | OPPO |
| R1-2008232 | Text proposal of physical layer procedure for NR sidelink | OPPO |
| R1-2008236 | Remaining open issues and corrections for mode 2 RA | OPPO |
| R1-2008237 | Corrections for FDM-based semi-static power split for in-device coexistence | OPPO |
| R1-2008334 | Correction on sidelink timing definition | Huawei, HiSilicon |
| R1-2008381 | Remaining issue on physical layer structure and procedure for sidelink in NR V2X | Panasonic Corporation |
| R1-2008387 | Remaining issues on physical layer structure for NR sidelink | Sharp |
| R1-2008388 | Remaining issues on resource allocation mode 1 for NR sidelink | Sharp |
| R1-2008389 | Remaining issues on resource allocation mode 2 for NR sidelink | Sharp |
| R1-2008390 | Remaining issues on synchronization mechanism for NR sidelink | Sharp |
| R1-2008391 | Remaining issues on physical layer procedures for NR sidelink | Sharp |
| R1-2008428 | Remaining Issues of Physical Layer Procedures | Apple |
| R1-2008429 | Remaining Issue of Sidelink Physical Layer Structure | Apple |
| R1-2008430 | Remaining Issues of Mode 1 Resource Allocation | Apple |
| R1-2008431 | Remaining Issues of Mode 2 Resource Allocation | Apple |
| R1-2008496 | Maintenance for PSFCH and PSCCH symbol on NR sidelink | ASUSTeK |
| R1-2008497 | Remaining issues on sidelink power control | ASUSTeK |
| R1-2008498 | Miscellaneous issues of SL HARQ-ACK reporting on PUCCH | ASUSTeK |
| R1-2008529 | Maintenance for sidelink physical layer structure | NTT DOCOMO, INC. |
| R1-2008530 | Maintenance for resource allocation mechanism mode 1 | NTT DOCOMO, INC. |
| R1-2008531 | Maintenance for resource allocation mechanism mode 2 | NTT DOCOMO, INC. |
| R1-2008532 | Maintenance for sidelink physical layer procedure | NTT DOCOMO, INC. |
| R1-2008533 | Maintenance for sidelink-related collision | NTT DOCOMO, INC. |
| R1-2008604 | Remaining Issues in Physical Layer Structure | Qualcomm Incorporated |
| R1-2008605 | Remaining Issues in Mode 1 Resource Allocation | Qualcomm Incorporated |
| R1-2008606 | Remaining Issues in Mode 2 Resource Allocation | Qualcomm Incorporated |
| R1-2008633 | Remaining issues for Mode 2 resource allocation in NR V2X | ASUSTeK |
| R1-2008665 | Remaining issues on physical layer structure for NR sidelink | vivo |
| R1-2008666 | Remaining issues on mode 1 resource allocation mechanism | vivo |
| R1-2008667 | Remaining issues on mode 2 resource allocation mechanism | vivo |
| R1-2008668 | Remaining issues on sidelink synchronization mechanism | vivo |
| R1-2008669 | Remaining issues on physical layer procedure for NR sidelink | vivo |
| R1-2008721 | Remaining issues on physical layer procedures for sidelink | KT Corp. |
| R1-2008750 | Discussion paper on the remaining issues in Rel. 16 for NR V2X | Ericsson |
| R1-2008751 | Draft_CR_TS38.211 | Ericsson |
| R1-2008752 | Draft_CR_TS38.212 | Ericsson |
| R1-2008753 | Draft_CR_TS38.213 | Ericsson |
| R1-2008754 | Draft_CR_TS38.214 | Ericsson |
| R1-2009230 | Feature lead summary#1 for physical layer procedure aspects in AI 7.2.4 | Moderator (LG Electronics) |
| R1-2009241 | Feature lead summary #1 for Sidelink synchronization mechanism | Moderator (CATT) |
| R1-2009294 | Feature lead summary on Mode-2 resource allocation issues in Rel.16 5G V2X | Moderator (Intel Corporation) |
| R1-2009374 | [Draft] Reply LS on sidelink configured grant handling | Ericsson |
| R1-2009402 | Corrections related to sidelink physical layer procedures | Moderator (LG Electronics), Huawei, HiSilicon, Ericsson, ASUSTeK, OPPO |
| R1-2009460 | Reply LS on sidelink configured grant handling | RAN1, Ericsson |
| R1-2009463 | Corrections on the use of TDRA and FDRA fields SCI for Mode 1 | Moderator (Ericsson) |
| R1-2009469 | Outcome and TP of email discussion [103-e-NR-Rel-16-V2X-04] | Moderator (Intel) |
| R1-2009470 | Outcome and TP of email discussion [103-e-NR-Rel-16-V2X-10] | Moderator (Intel) |
| R1-2009471 | Outcome of email discussion [103-e-NR-Rel-16-V2X-13] | Moderator (Intel) |
| R1-2009472 | [Draft] LS on R16 V2X Mode-2 agreements to capture in MAC specification | Intel |
| R1-2009473 | [Draft] LS reply on RAN2 agreements and RAN1 related issues | Intel |
| R1-2009474 | LS on R16 V2X Mode-2 agreements to capture in MAC specification | RAN1, Intel |
| R1-2009475 | LS reply on RAN2 agreements and RAN1 related issues | RAN1, Intel |
| R1-2009497 | Corrections on the use of TDRA and FDRA fields SCI for Mode 1 | Moderator (Ericsson) |
| R1-2009507 | Correction on sidelink timing definition | Moderator (CATT), Huawei, HiSilicon, LG Electronics |
| R1-2009510 | FL summary 1 for thread 3 on Maintenance for 5G V2X with NR sidelink – Mode 1 | Moderator (Ericsson) |
| R1-2009511 | FL summary 1 for thread 9 on Maintenance for 5G V2X with NR sidelink – Mode 1 | Moderator (Ericsson) |
| R1-2009512 | FL summary 1 for thread 14 on Maintenance for 5G V2X with NR sidelink – Mode 1 | Moderator (Ericsson) |
| R1-2009516 | Corrections for the prioritization between uplink transmission and sidelink transmission/reception | Moderator (LG Electronics) |
| R1-2009517 | Corrections related to the sidelink slot index | Moderator (LG Electronics), Huawei, HiSilicon |
| R1-2009518 | Corrections related to the sidelink slot index | Moderator (LG Electronics), Huawei, HiSilicon |
| R1-2009520 | Correction on sidelink pathloss calculation for S-SSB power control | Moderator (CATT), vivo, Ericsson |
| R1-2009522 | [Draft] LS on configurable values for sl-DCI-ToSL-Trans | Ericsson |
| R1-2009531 | Correction on sidelink TDD configuration for OoC Ues | Moderator (CATT), LG Electronics, vivo |
| R1-2009532 | Correction on sidelink resource pool determination based on PSBCH | Moderator (CATT), LG Electronics |
| R1-2009535 | Feature lead summary #2 for Sidelink synchronization mechanism | Moderator (CATT) |
| R1-2009547 | [Draft] Introduction of the preparation time for SL retransmissions in Mode 1 | Moderator (Ericsson) |
| R1-2009548 | [Draft] Introduction of the preparation time for SL retransmissions in Mode 1 | Moderator (Ericsson) |
| R1-2009577 | LS on configurable values for sl-DCI-ToSL-Trans | RAN1, Ericsson |
| R1-2009578 | Introduction of the preparation time for SL retransmissions in Mode 1 | Moderator (Ericsson) |
| R1-2009579 | Introduction of the preparation time for SL retransmissions in Mode 1 | Moderator (Ericsson) |
| R1-2009592 | Corrections on sidelink for PHY layer structure | Moderator (Samsung), Ericsson, CATT |
| R1-2009593 | Correction on periodicity of resource pool bitmap | Moderator (Samsung), OPPO |
| R1-2009594 | Correction on redundancy version for PSSCH | Moderator (Samsung), ZTE, Sanechips |
| R1-2009640 | Corrections on sidelink for PHY layer structure | Moderator (Samsung), Ericsson, CATT, Huawei, HiSilicon |
| R1-2009641 | Correction on periodicity of resource pool bitmap | Moderator (Samsung), OPPO, Huawei, HiSilicon |
| R1-2009642 | Correction on redundancy version for PSSCH | Moderator (Samsung), ZTE, Sanechips, Huawei, HiSilicon |
| R1-2009661 | LS reply on RAN1 agreement on pre-emption | RAN1, Intel |
| R1-2009662 | Correction on SL PT-RS sequence generation | Moderator (Samsung), Apple, Sharp |
| R1-2009663 | Correction on PSFCH mapping | Moderator (Samsung), Huawei, HiSilicon, NTT DOCOMO, Ericsson |
| R1-2009664 | Correction on PSFCH and PSCCH mapping | Moderator (Samsung), ZTE, Sanechips, Huawei, HiSilicon, NTT DOCOMO, Ericsson |
| R1-2009674 | Correction on PSFCH and PSCCH mapping | Moderator (Samsung), ZTE, Sanechips, Huawei, HiSilicon, NTT DOCOMO, Ericsson |
| R1-2009763 | Feature Lead Summary of emails discussion [103-e-NR-Rel-16-V2X-07] | Moderator (LG Electronics) |
| R1-2009769 | Correction on sidelink TDD configuration for OoC Ues | Moderator (CATT), LG Electronics, vivo |
| R1-2009845 | FL summary for thread 2 on Maintenance for 5G V2X with NR sidelink | Moderator(Samsung) |
| R1-2009846 | FL summary for thread 8 on Maintenance for 5G V2X with NR sidelink | Moderator(Samsung) |
| R1-2009847 | FL summary for thread 1 on Maintenance for 5G V2X with NR sidelink | Moderator(Samsung) |
| 7.2.5 | Maintenance of Physical Layer Enhancements for NR URLLC | |
| R1-2007634 | Corrections on PDCCH enhancements | Huawei, HiSilicon |
| R1-2007635 | Corrections on scheduling and HARQ | Huawei, HiSilicon |
| R1-2007636 | Corrections on SPS enhancements | Huawei, HiSilicon |
| R1-2007703 | Maintenance of PDCCH for NR URLLC | Ericsson |
| R1-2007704 | Maintenance of UCI for NR URLLC | Ericsson |
| R1-2007705 | Maintenance of Scheduling/HARQ for NR URLLC | Ericsson |
| R1-2007706 | Corrections for NR URLLC/IIoT | Ericsson |
| R1-2007732 | Discussion on extension of M-TRP operation for Rel-15 cells in CA case 3 | ZTE |
| R1-2007733 | Discussion and text proposals on UL control enhancements for NR URLLC | ZTE |
| R1-2007734 | Text proposals for intra-UE multiplexing and PUSCH preparation procedure time | ZTE |
| R1-2007735 | Text proposal for UE processing order between UL CI and power scaling calculation in UL CA | ZTE |
| R1-2007781 | A remaining issue on the reference of spatial relation for a PUSCH scheduled by DCI format 0_0 | Fujitsu |
| R1-2007782 | A remaining issue on timing for applying SCell activation or deactivation | Fujitsu |
| R1-2007814 | Remaining issues on PDCCH enhancements and inter-UE UL multiplexing | CATT |
| R1-2007815 | Remaining issues on UCI enhancements | CATT |
| R1-2007816 | Remaining issues on intra-UE prioritization | CATT |
| R1-2007817 | Discussion on overlapping between CG PUSCH and DG PUSCH | CATT |
| R1-2007937 | Draft TP on enhanced PDCCH monitoring for eURLLC | Intel Corporation |
| R1-2007988 | Remaining issues on URLLC | ETRI |
| R1-2008056 | PHR issues related to URLLC/IIOT WI | LG Electronics |
| R1-2008109 | Remaining issues of enhancements to scheduling/HARQ | Spreadtrum Communications |
| R1-2008135 | Maintanence on PDCCH as PDSCH SLIV reference | Samsung |
| R1-2008136 | Draft CR on Type-2 HARQ-ACK codebook | Samsung |
| R1-2008137 | Maintanence on SPS PDSCH | Samsung |
| R1-2008138 | Draft CR on SPS release for PDSCH with aggregation | Samsung |
| R1-2008276 | Text proposal for PUCCH carrying HARQ-ACK | OPPO |
| R1-2008277 | Remaining issues on scheduling and HARQ | OPPO |
| R1-2008278 | Remaining issues on DL SPS enhancement | OPPO |
| R1-2008297 | Draft CRs on PUCCH repetition handling with PHY priorities and Timing of SCell activation/deactivation for sub-slot PUCCH | Nokia, Nokia Shanghai Bell |
| R1-2008298 | Support of Type-1 HARQ-ACK Codebook with PUCCH sub-slot configurations (incl. draft CR) | Nokia, Nokia Shanghai Bell |
| R1-2008303 | Maintenance of Rel-16 URLLC intra-UE prioritization enhancements (incl. draft CRs) | Nokia, Nokia Shanghai Bell |
| R1-2008304 | Out-of-order CBG based PUSCH re-transmission and PHR / power scaling with UL cancelation | Nokia, Nokia Shanghai Bell |
| R1-2008307 | Inter-UE prioritization/multiplexing | InterDigital, Inc. |
| R1-2008392 | Maintenance on UL PDCCH search space sharing for CA for NR URLLC | Sharp |
| R1-2008393 | Remaining issue on subselection indication for DCI format 0_1/0_2 for NR URLLC | Sharp |
| R1-2008432 | Remaining issues on UCI and PUSCH enhancements for eURLLC | Apple |
| R1-2008433 | PHR and Power Scaling in case of Inter-UE Cancellation for eURLLC | Apple |
| R1-2008434 | Maintenance of configured grant design in Physical Layer Enhancements for NR URLLC | Apple |
| R1-2008435 | Maintenance of PDCCH design in Physical Layer Enhancements for NR URLLC | Apple |
| R1-2008486 | Maintenance of PDCCH Enhancements for Rel-16 URLLC | Quectel |
| R1-2008534 | Corrections on UCI enhancement for Rel-16 URLLC | NTT DOCOMO, INC. |
| R1-2008535 | Corrections on scheduling/HARQ for Rel-16 URLLC | NTT DOCOMO, INC. |
| R1-2008562 | Remaining issue on the HARQ-ACK/PUSCH priority | ITRI |
| R1-2008607 | Remaining issue on HARQ and scheduling for URLLC | Qualcomm Incorporated |
| R1-2008608 | Remaining issues on UCI enhancements for URLLC | Qualcomm Incorporated |
| R1-2008609 | Remaining issues on PUSCH enhancements for URLLC | Qualcomm Incorporated |
| R1-2008634 | Remaining issue for TCI field | ASUSTeK |
| R1-2008636 | Remaining issues for DL SPS enhancement | ASUSTeK |
| R1-2008670 | PDCCH enhancements for URLLC | vivo |
| R1-2008671 | UCI enhancements for URLLC | vivo |
| R1-2008672 | Enhancement for Scheduling/HARQ | vivo |
| R1-2008673 | UL inter UE Tx prioritization for URLLC | vivo |
| R1-2008725 | Corrections on HARQ-ACK codebooks for Rel-16 URLLC | WILUS Inc. |
| R1-2008772 | Correction on sub-slot partition | Huawei, HiSilicon |
| R1-2008846 | Summary on maintenance of other aspects for URLLC/IIOT | Moderator (LG Electronics) |
| R1-2009044 | Summary#1 on UCI enhancements for R16 URLLC | OPPO |
| R1-2009081 | Summary of remaining issues on inter-UE prioritization/multiplexing | Moderator (vivo) |
| R1-2009082 | Feature lead summary on eCG for NR eURLLC | Moderator (vivo) |
| R1-2009334 | Feature lead summary on PUSCH enhancements for NR eURLLC (AI 7.2.5) | Moderator (Apple Inc.) |
| R1-2009335 | Summary of [103-e-NR-L1enh-URLLC-05] | Moderator (Apple Inc.) |
| R1-2009336 | Summary #1 of the Remaining Issues on HARQ and Scheduling Enhancements for URLLC | Moderator (Qualcomm) |
| R1-2009337 | Summary of email discussion on preparation phase for Rel-16 URLLC/IIoT | Moderator (Huawei) |
| R1-2009338 | Feature lead summary on PDCCH enhancements | Moderator (Huawei) |
| R1-2009339 | Summary #1 of email discussion [103-e-NR-L1enh-URLLC-01] on remaining issues on enhanced PDCCH monitoring capability | Moderator (Huawei) |
| R1-2009340 | Summary #1 of email discussion [103-e-NR-L1enh-URLLC-02] on remaining issues on DCI format design | Moderator (Huawei) |
| R1-2009412 | Summary#1 of email thread [103-e-NR-L1enh_URLLC-UCI_Enh-03] | Moderator (OPPO) |
| R1-2009462 | Summary of email discussion [103-e-NR-L1enh-URLLC-06] | Moderator (vivo) |
| R1-2009478 | Correction on data rate restriction in a slot for PUSCH repetition Type B | Moderator (Apple Inc.) |
| R1-2009636 | Correction on Type2 HARQ-ACK codebook construction | Moderator (Huawei) |
| R1-2009637 | Correction on UL grant Type 2 PUSCH release for search space sharing | Moderator (Huawei), Sharp |
| R1-2009638 | Correction on Transmission configuration indication in DCI format 1_2 | Moderator (Huawei), ASUSTeK |
| R1-2009639 | Correction on PDCCH monitoring on cell(s) configured with Rel-15 PDCCH monitoring capability | Moderator (Huawei) |
| R1-2009680 | Reply LS on Intra UE Prioritization Scenario | RAN1, vivo |
| R1-2009684 | Summary of email discussion [103-e-NR-L1enh-URLLC-07] | Moderator (vivo) |
| R1-2009770 | Summary #2 of the Remaining Issues on HARQ and Scheduling Enhancements for URLLC | Moderator (Qualcomm) |
| R1-2009790 | CR on handling overlapping PUCCH/PUSCH transmissions with repetitions and with different priorities | Moderator (OPPO) |
| R1-2009827 | Session notes for 7.2.5 (Maintenance of Physical Layer Enhancements for NR URLLC/IIoT) | Ad-hoc Chair (Samsung) |
| 7.2.6 | Maintenance of Enhancements on MIMO for NR | |
| R1-2007748 | Maintenance of multi-beam operation | ZTE |
| R1-2007749 | Draft CR on UL full power transmission Mode 1 | ZTE |
| R1-2007750 | Maintenance of Multi-TRP enhancements | ZTE |
| R1-2007818 | Discussion on remaining issues of multi-TRP/panel transmission | CATT |
| R1-2007819 | Correction on PTRS for UL full power transmission | CATT |
| R1-2007820 | Remaining Issues on multi-beam operation enhancement | CATT |
| R1-2007909 | Correction on L1-SINR Resource Setting | FUTUREWEI |
| R1-2007938 | Corrections to multi TRP | Intel Corporation |
| R1-2008093 | Discussion on remaining issues for multi-TRP operation | Spreadtrum Communications |
| R1-2008094 | Discussion on remaining issues on full TX power for UL transmission | Spreadtrum Communications |
| R1-2008139 | On maintenance of Rel.16 multi-beam operation | Samsung |
| R1-2008140 | Summary for Rel.16 NR eMIMO maintenance | Moderator (Samsung) |
| R1-2008141 | On Rel.16 multi-TRP/panel transmission | Samsung |
| R1-2008142 | On UL full power transmission | Samsung |
| R1-2008211 | Text proposals for enhancements on multi-TRP and panel Transmission | OPPO |
| R1-2008212 | Correction for default TCI state of AP CSI-RS for M-TRP | OPPO |
| R1-2008213 | Text Proposals for Multi-beam Operation Enhancement | OPPO |
| R1-2008293 | Maintenance on multi-TRP operation | Lenovo, Motorola Mobility |
| R1-2008324 | Correction on L1-SINR reporting | Huawei, HiSilicon |
| R1-2008325 | Correction on the maximum number of CORESETs for Multi-DCI Transmission | Huawei, HiSilicon |
| R1-2008326 | Correction on the index value range of CORESET for Multi-DCI Transmission | Huawei, HiSilicon |
| R1-2008345 | Remaining issues on multi-beam operation | Sony |
| R1-2008436 | Remaining issues on Rel-16 Multi-TRP enhancement | Apple |
| R1-2008437 | Remaining issues on Rel-16 Beam Management | Apple |
| R1-2008514 | Remaining issues on multi-beam operation | MediaTek Inc. |
| R1-2008536 | Updated proposal of PUCCH spatial relation after CBRA-BFR in Rel.16 | NTT DOCOMO, INC, Nokia, Nokia Shanghai Bell, InterDigital |
| R1-2008569 | Corrections on Multi-TRP PDCCH | Quectel |
| R1-2008570 | Draft CR on multi-TRP/panel transmission | LG Electronics |
| R1-2008571 | Draft CR on beam management | LG Electronics |
| R1-2008572 | Text proposals on full Tx power UL transmission | LG Electronics |
| R1-2008610 | Remaining Issues on Multi-TRP Enhancements | Qualcomm Incorporated |
| R1-2008611 | Remaining issue on multi-beam operation | Qualcomm Incorporated |
| R1-2008635 | Draft CR on TCI states for Aperiodic CSI-RS | Ericsson |
| R1-2008637 | Draft CR on DL SPS based PDSCH repetitions | Ericsson |
| R1-2008638 | Draft CR on TCI state codepoint mapping for DCI format 1_2 | Ericsson |
| R1-2008640 | Draft CR on QCL terminology alignment | Nokia, Nokia Shanghai Bell |
| R1-2008641 | draft CR on higher layer parameter enabling L1-SINR operation procedures | Nokia, Nokia Shanghai Bell |
| R1-2008674 | Remaining issues and corrections on multi beam related issues | vivo |
| R1-2008675 | Corrections on multi TRP related issues | vivo |
| R1-2008676 | Miscellaneous corrections on power control | vivo |
| R1-2008723 | Maintenance of Rel-16 Multi-TRP operation | Nokia, Nokia Shanghai Bell |
| R1-2009233 | Initial summary of email thread [103-e-NR-eMIMO-01] | Moderator (LG Electronics) |
| R1-2009234 | Final summary of email thread [103-e-NR-eMIMO-01] | Moderator (LG Electronics) |
| R1-2009332 | Summary of email discussion 103-e-NR-eMIMO-02 | Moderator (Apple Inc.) |
| R1-2009333 | Outcome of email discussion 103-e-NR-eMIMO-02 | Moderator (Apple Inc.) |
| R1-2009401 | Corrections for default TCI state of AP CSI-RS in multi-TRP | Moderator (OPPO), ZTE, Apple, vivo, Ericsson |
| R1-2009414 | Summary of [103-e-NR-eMIMO-04] email discussion | Moderator (vivo) |
| R1-2009449 | LS on TPMI grouping capability | RAN1, vivo |
| R1-2009456 | Corrections for the issue of PDCCH and PDSCH colliding in multi-TRP | Moderator (OPPO), ZTE, Apple |
| R1-2009457 | Correction on TCI state codepoint mapping for DCI format 1_2 | Moderator(LG Electronics), Ericsson, Samsung |
| R1-2009458 | Correction on UL power control | Moderator(LG Electronics), ZTE |
| R1-2009506 | CR on Interference Measurement Resource for L1-SINR | Moderator (Apple), LG Electronics |
| R1-2009519 | LS on CBRA based Beam Failure Recovery | RAN1, Apple |
| R1-2009685 | CR on CBRA based BFR | Moderator (Apple), NTT DOCOMO, INC, Nokia, Nokia Shanghai Bell, InterDigital |
| R1-2009686 | CR on Measurement Restriction for L1-SINR | Moderator (Apple), vivo |
| R1-2009828 | Session notes for 7.2.6 (Maintenance of Enhancements on MIMO for NR) | Ad-hoc Chair (Samsung) |
| 7.2.7 | Maintenance of UE Power Saving for NR | |
| R1-2007821 | Remaining issues on UE Power Saving | CATT |
| R1-2007970 | Remaining issues of Rel-16 power saving | ZTE |
| R1-2008104 | Remaining issues on UE power saving | Spreadtrum Communications |
| R1-2008143 | Remaining issues for Rel-16 UE power saving | Samsung |
| R1-2008331 | Remaining issues for Rel-16 UE power saving | Huawei, HiSilicon |
| R1-2008509 | Remaining issues on UE power saving | MediaTek Inc. |
| R1-2008565 | Maintenance for UE power saving | Ericsson |
| R1-2008677 | Remaining issues on UE power saving | vivo |
| R1-2008732 | On open issues related to Rel-16 UE power saving | Nokia, Nokia Shanghai Bell |
| R1-2009588 | Summary of Rel-16 UE power saving email discussion [103e-NR-Rel-16-PowSav-01] | Moderator (CATT) |
| R1-2009589 | Correction on L1-RSRP and Minimum scheduling offset | Moderator (CATT), MediaTek |
| 7.2.8 | Maintenance of NR positioning support | |
| R1-2007574 | Rel-16 positioning corrections | Huawei, HiSilicon |
| R1-2007751 | Draft CR on measurement gap configuration for DL PRS reception | ZTE |
| R1-2007752 | Draft CR on the definition of nr-DL-PRS-expectedRSTD-r16 | ZTE |
| R1-2007822 | Discussion on configuration parameters related to SRS-Pos | CATT |
| R1-2007823 | Discussion on linear value of SRS power split by UE | CATT |
| R1-2007999 | Remaining issues on DL PRS | CMCC |
| R1-2008214 | Text Proposals on NR Positioning Procedure | OPPO |
| R1-2008215 | Text Proposals on RS for Positioning | OPPO |
| R1-2008414 | Discussions on remaining issues on Rel-16 NR positioning | LG Electronics |
| R1-2008580 | Editorial Corrections on Rel-16 NR positioning | LG Electronics |
| R1-2008678 | Remaining issues on prioritization of positioning assistance data | vivo |
| R1-2008679 | Remaining issues on TRP ID for NR positioning | vivo |
| R1-2008760 | Corrections to 38.211 for NR positioning | Ericsson |
| R1-2008761 | Corrections to 38.214 for NR positioning | Ericsson |
| R1-2008789 | Correction to PRS duration calculation for PRS processing | Huawei, HiSilicon |
| R1-2009239 | Feature Lead Summary for NR Positioning Maintenance AI 7.2.8 | Moderator (Intel Corporation, CATT, Ericsson, Qualcomm) |
| R1-2009240 | Feature Lead Summary for NR Positioning Maintenance AI 7.2.8 | Moderator (Intel Corporation), CATT, Ericsson, Qualcomm |
| R1-2009419 | Output for email discussion [103-e-NR-Pos-02] | Moderator (Ericsson) |
| R1-2009434 | Outcome of RAN WG1 E-mail Discussion [103-e-NR-Pos-01] - AI 7.2.8 | Moderator (Intel) |
| R1-2009560 | Draft CR Corrections to 38.211 for NR positioning | Moderator (Intel Corporation), Ericsson |
| R1-2009561 | Draft CR Correction to DL PRS duration calculation for DL PRS processing | Moderator (Intel Corporation), Huawei, HiSilicon |
| R1-2009562 | Draft CR on DL PRS resource prioritization for UE measurements | Moderator (Intel Corporation), LGE |
| R1-2009597 | Draft CR on the configuration of spatial relation for the SRS for positioning | Moderator (Ericsson), CATT |
| R1-2009598 | Draft CR for replacement of cell terminology in PRS reception procedure | Moderator (Ericsson), OPPO, Nokia, Nokia Shanghai Bell |
| R1-2009599 | Draft CR for correction on the QCL description between PRS and SSB | Moderator (Ericsson), OPPO, Huawei, HiSilicon |
| R1-2009600 | Draft CR for parameter name alignment and reference corrections in PRS reception procedure | Moderator (Ericsson), OPPO, LG Electronics |
| R1-2009692 | Corrections to 38.211 for NR positioning | Moderator (Intel Corporation), Ericsson |
| R1-2009693 | Correction to DL PRS duration calculation for DL PRS processing | Moderator (Intel Corporation), Huawei, HiSilicon |
| R1-2009694 | CR on DL PRS resource prioritization for UE measurements | Moderator (Intel Corporation), LGE |
| R1-2009738 | CR on the configuration of spatial relation for the SRS for positioning | Moderator (Ericsson), CATT |
| R1-2009739 | CR for replacement of cell terminology in PRS reception procedure | Moderator (Ericsson), OPPO, Nokia, Nokia Shanghai Bell |
| R1-2009740 | CR for correction on the QCL description between PRS and SSB | Moderator (Ericsson), OPPO, Huawei, HiSilicon |
| R1-2009741 | CR for parameter name alignment and reference corrections in PRS reception procedure | Moderator (Ericsson), OPPO, LG Electronics, Ericsson |
| R1-2009767 | CR for correction on the QCL description between PRS and SSB | Moderator (Ericsson), OPPO, Huawei, HiSilicon |
| R1-2009829 | Session notes for 7.2.8 (Maintenance of NR positioning support) | Ad-Hoc Chair (Ericsson) |
| 7.2.9 | Maintenance of NR Mobility Enhancements | |
| R1-2007593 | Remaining issues on DAPS | Huawei, HiSilicon |
| R1-2007738 | Draft CR on intra-frequency DAPS handover | ZTE |
| R1-2008144 | Draft CR on clarification of processing capability on DAPS HO dropping timeline | Samsung |
| R1-2008209 | Correction to DAPS HO | Ericsson |
| R1-2008502 | Remaining issues on per CC UE capability and UL cancellation for DAPS-HO | MediaTek Inc. |
| R1-2008733 | Remaining physical layer aspects of dual active protocol stack based HO | Nokia, Nokia Shanghai Bell |
| R1-2008870 | Pre-meeting Issue Summary for NR Mobility Enhancements | Intel Corporation |
| R1-2008871 | Pre-meeting Issue Summary for NR Mobility Enhancements | Moderator (Intel Corporation) |
| R1-2009353 | [103-e-NR-Mob-Enh-01] Discussions Summary #1 | Moderator (Intel Corporation) |
| R1-2009354 | [103-e-NR-Mob-Enh-02] Discussions Summary #1 | Moderator (Intel Corporation) |
| R1-2009481 | Correction on uplink transmission cancellation for DAPS handover | Moderator (Intel Corporation) |
| R1-2009482 | Correction on PUSCH processing capability for DAPS handover | Moderator (Intel Corporation) |
| R1-2009483 | Correction on intra-frequency DAPS handover | Moderator (Intel Corporation) |
| R1-2009525 | Correction on uplink transmission cancellation for DAPS handover | Moderator (Intel Corporation), MediaTek |
| R1-2009526 | Correction on PUSCH processing capability for DAPS handover | Moderator (Intel Corporation), Samsung |
| R1-2009527 | Correction on intra-frequency DAPS handover | Moderator (Intel Corporation), Ericsson, Qualcomm |
| R1-2009541 | [103-e-NR-Mob-Enh-01] Discussions Summary #2 | Moderator (Intel Corporation) |
| R1-2009542 | [103-e-NR-Mob-Enh-02] Discussions Summary #2 | Moderator (Intel Corporation) |
| R1-2009681 | [Draft] LS on support of NUL and SUL during DAPS handover | Intel Corporation |
| R1-2009682 | LS on support of NUL and SUL during DAPS handover | RAN1, Intel Corporation |
| R1-2009746 | [103-e-NR-Mob-Enh-02] Discussions Summary #3 | Moderator (Intel Corporation) |
| R1-2009830 | Session notes for 7.2.9 (Maintenance of NR Mobility Enhancements) | Ad-Hoc Chair (Ericsson) |
| 7.2.10 | Maintenance of Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements (LTE, NR) | |
| R1-2007578 | Remaining issues on CA | Huawei, HiSilicon |
| R1-2007736 | Remaining Issues of Power Control for NR-DC and Cross-Carrier Scheduling | ZTE |
| R1-2007737 | Remaining Issues of SCell Dormancy, Single Tx and Unaligned Frame Boundary | ZTE |
| R1-2007806 | Remaining issues on inter-band CA with unaligned frame boundary | CATT |
| R1-2007807 | Corrections on HARQ-ACK codebook for secondary PUCCH group | CATT |
| R1-2008113 | Correction to dormancy indication outside Active Time | NEC |
| R1-2008145 | Remaining issues for Scell dormancy | Samsung |
| R1-2008203 | Remaining issues on dormancy | Nokia, Nokia Shanghai Bell |
| R1-2008275 | BWP switching delay issues and Scell dormancy | OPPO |
| R1-2008503 | Remaining issues on Rel-16 uplink power control for supporting NR-NR dual-connectivity | MediaTek Inc. |
| R1-2008504 | Remaining issues on Rel-16 carrier aggregation | MediaTek Inc. |
| R1-2008566 | Draft CR to 38.213 on corrections for SCell dormancy | Ericsson |
| R1-2008567 | Maintenance for other MR-DC topics | Ericsson |
| R1-2008612 | Remaining issue on NR-DC power-control | Qualcomm Incorporated |
| R1-2008613 | Remaining issue on SCell dormancy | Qualcomm Incorporated |
| R1-2008680 | Remaining issues on MR-DC and CA enhancements | vivo |
| R1-2008694 | Discussion for Rel-16 DC uplink power control | Nokia, Nokia Shanghai Bell |
| R1-2008719 | Interoperation between cross-carrier scheduling and multiple TRPs | ASUSTeK |
| R1-2008897 | FL summary on support of unaligned frame boundary for R16 NR inter-band CA | Moderator (CMCC) |
| R1-2009210 | Summary of maintenance issues for SCell Dormancy | Moderator (Ericsson) |
| R1-2009218 | Feature Lead summary on singe Tx enhancements, and cross carrier scheduling and A-CSI RS triggering | Moderator (Nokia) |
| R1-2009219 | Moderator summary of the 4 feature lead summaries of 7.2.10 in preparation of RAN1#103-e | Moderator (Nokia) |
| R1-2009231 | Feature lead summary #1 on UL Power Control for NN-DC | Moderator (Apple Inc.) |
| R1-2009630 | Summary of Email discussion [103-e-NR-MRDC-CA-02] | Moderator (Nokia) |
| R1-2009631 | LS on HARQ-ACK codebook configuration for secondary PUCCH group | RAN1, Nokia |
| R1-2009632 | 38.213 CR for NR-DC power control | Moderator (Nokia), MediaTek, Nokia, Nokia Shanghai Bell, ZTE |
| R1-2009633 | 38.213 CR Correction on HARQ-ACK codebook for secondary PUCCH group | Moderator (Nokia), CATT |
| R1-2009634 | 36.213 CR on Single UL Tx for EN-DC | Moderator (Nokia), ZTE |
| R1-2009755 | Corrections for SCell dormancy indication | Moderator (Ericsson), ZTE |
| R1-2009756 | Corrections for A-CSI triggering with unaligned CA | Moderator (Ericsson) |
| R1-2009810 | Summary of Email discussion [103-e-NR-MRDC-CA-01] | Moderator (Ericsson) |
| R1-2009831 | Session notes for 7.2.10 (Maintenance of Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements) | Ad-Hoc Chair (Ericsson) |
| 7.2.11 | NR Rel-16 UE Features | |
| R1-2007739 | Discussion on NR Rel-16 UE Features | ZTE |
| R1-2007808 | Remaining issues on Rel-16 UE features | CATT |
| R1-2007913 | Summary of UE features for IAB | Moderator (AT&T) |
| R1-2007914 | Summary of UE features for 5G V2X | Moderator (AT&T) |
| R1-2007915 | Summary of UE features for eMIMO | Moderator (AT&T) |
| R1-2007916 | Summary of UE features for UE power savings | Moderator (AT&T) |
| R1-2007917 | Summary of UE features for NR mobility enhancements | Moderator (AT&T) |
| R1-2007939 | Rel-16 UE features | Intel Corporation |
| R1-2008146 | Remaining issues on NR Rel-16 UE features | Samsung |
| R1-2008216 | Discussion on Rel-16 UE features | OPPO |
| R1-2008333 | Remaining details of Rel-16 NR UE features | Huawei, HiSilicon |
| R1-2008427 | Discussions on NR Rel-16 UE features | Apple |
| R1-2008490 | Discussion on Rel-16 UE features for NR-U | LG Electronics |
| R1-2008508 | Remaining issues on Rel-16 UE feature list | MediaTek Inc. |
| R1-2008537 | Discussion on NR Rel-16 UE features | NTT DOCOMO, INC. |
| R1-2008538 | Summary on UE features for two-step RACH | Moderator (NTT DOCOMO, INC.) |
| R1-2008539 | Summary on UE features for NR-U | Moderator (NTT DOCOMO, INC.) |
| R1-2008540 | Summary on UE features for URLLC/IIoT | Moderator (NTT DOCOMO, INC.) |
| R1-2008541 | Summary on UE features for NR positioning | Moderator (NTT DOCOMO, INC.) |
| R1-2008542 | Summary on UE features for MR-DC/CA | Moderator (NTT DOCOMO, INC.) |
| R1-2008543 | Summary on UE features for CLI/RIM | Moderator (NTT DOCOMO, INC.) |
| R1-2008544 | Summary on UE features for TEIs | Moderator (NTT DOCOMO, INC.) |
| R1-2008545 | Summary on NR UE features for others | Moderator (NTT DOCOMO, INC.) |
| R1-2008614 | Discussion on NR Rel-16 UE features | Qualcomm Incorporated |
| R1-2008631 | Discussion on NR Rel-16 UE features | Qualcomm Incorporated |
| R1-2008639 | Remaining details of Rel-16 NR UE features | Ericsson |
| R1-2008681 | Remaining issues on NR Rel-16 UE features | vivo |
| R1-2008737 | Remaining issues on NR UE features | Nokia, Nokia Shanghai Bell |
| R1-2009323 | Summary on [103-e-NR-UEFeature-NRU-01] | Moderator (NTT DOCOMO, INC.) |
| R1-2009324 | Summary on [103-e-NR-UEFeature-URLLC/IIoT-01] | Moderator (NTT DOCOMO, INC.) |
| R1-2009325 | Summary on [103-e-NR-UEFeature-MRDCCA-01] | Moderator (NTT DOCOMO, INC.) |
| R1-2009326 | Summary on [103-e-NR-UEFeature-TEI-01] | Moderator (NTT DOCOMO, INC.) |
| R1-2009327 | Summary on [103-e-NR-UEFeature-Others-01] | Moderator (NTT DOCOMO, INC.) |
| R1-2009328 | LS on updated Rel-16 RAN1 UE features lists for NR | RAN1, NTT DOCOMO |
| R1-2009329 | Updated RAN1 UE features list for Rel-16 NR | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2009346 | Summary of email discussion/approval [103-e-NR-UEFeatures-V2X-01] | Moderator (AT&T) |
| R1-2009347 | Summary of email discussion/approval [103-e-NR-UEFeatures-MobEnh-01] | Moderator (AT&T) |
| R1-2009348 | Summary of email discussion/approval [103-e-NR-UEFeatures-eMIMO-01] | Moderator (AT&T) |
| R1-2009349 | Session Notes of AI 7.2.11 | Ad-Hoc Chair (AT&T) |
| R1-2009385 | Reply LS on UE capability on wideband carrier operation for NR-U | RAN1, MediaTek |
| R1-2009496 | Reply LS to RAN2 on beamSwitchTiming | RAN1, vivo |
| R1-2009570 | LS reply on cell-grouping UE capability for synchronous NR-DC | RAN1, Qualcomm Incorporated |
| R1-2009585 | Updated RAN1 UE features list for Rel-16 NR | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2009586 | LS on updated Rel-16 RAN1 UE features lists for NR | RAN1, AT&T, NTT DOCOMO |
| R1-2009635 | Reply LS on UE capability for V2X | RAN1, OPPO |
| R1-2009643 | Reply LS on maximum data rate for NR sidelink | RAN1, OPPO |
| 7.2.12 | Other | |
| R1-2007911 | Discussion on RIM with partially overlapping bandwidths | Ericsson |
| R1-2007940 | Draft TPs regarding umber of configurable CSI-RS resources per MO | Intel Corporation |
| R1-2008210 | Correction to beam switch timing | Ericsson |
| R1-2008546 | Summary on Rel-16 NR TEI related discussion | Moderator (NTT DOCOMO, INC.) |
| R1-2008682 | Correction on beamswitch timing for aperiodic TRS and increased number of CSI-RS for mobility per MO | vivo |
| R1-2008736 | Increase in number of CSI-RS for L3 mobility | Nokia, Nokia Shanghai Bell |
| R1-2008796 | Other remaining issues for NR MIMO in Rel-16 | Huawei, HiSilicon |
| R1-2009330 | Summary on [103-e-NR-TEIs-01] | Moderator (NTT DOCOMO, INC.) |
| R1-2009331 | Summary on [103-e-NR-TEIs-02] | Moderator (NTT DOCOMO, INC.) |
| R1-2009369 | [Draft] Reply LS on number of configurable CSI-RS resources per MO | Intel Corporation |
| R1-2009444 | Reply LS on number of configurable CSI-RS resources per MO | RAN1, Intel Corporation |
| R1-2009447 | Correction on beam switch timing for aperiodic TRS | Moderator (NTT DOCOMO), vivo |
| R1-2009448 | Correction on increased number of CSI-RS for mobility per MO | Moderator (NTT DOCOMO) |
| R1-2009494 | Correction to beam switch timing | Moderator (NTT DOCOMO, INC.), Ericsson, Huawei, ZTE |
| 8.1 | Further enhancements on MIMO for NR | |
| R1-2009832 | Session notes for 8.1 (Further enhancements on MIMO for NR) | Ad-hoc Chair (Samsung) |
| 8.1.1 | Enhancements on Multi-beam Operation | |
| R1-2007546 | Enhancement on multi-beam operation | FUTUREWEI |
| R1-2007586 | Enhancements on multi-beam operation in Rel-17 | Huawei, HiSilicon |
| R1-2007626 | Discussions on Multi-beam Enhancement | InterDigital, Inc. |
| R1-2007644 | Further discussion on multi beam enhancement | vivo |
| R1-2007763 | Enhancements on Multi-beam Operation | ZTE |
| R1-2007824 | Discussion on enhancement on multi-beam operation | CATT |
| R1-2008000 | Enhancements on multi-beam operation | CMCC |
| R1-2008147 | Moderator summary for multi-beam enhancement | Moderator (Samsung) |
| R1-2008148 | Multi-Beam Enhancements | Samsung |
| R1-2008217 | Enhancements on Multi-beam Operation | OPPO |
| R1-2008308 | Enhancements on NR multi-beam operation | AT&T |
| R1-2008346 | Considerations on the enhancement of multi-beam operation | Sony |
| R1-2008438 | Views on Rel-17 Beam Management enhancement | Apple |
| R1-2008573 | Enhancements on Multi-beam Operation | LG Electronics |
| R1-2008899 | Enhancements on multi-beam operation | Fraunhofer IIS, Fraunhofer HHI |
| R1-2008903 | Enhancements on Multi-beam Operation | Nokia, Nokia Shanghai Bell |
| R1-2008910 | Enhancements on Multi-beam Operation | Lenovo, Motorola Mobility |
| R1-2008943 | Discussion on multi-beam operation | NEC |
| R1-2008956 | Enhancement on multi-beam operation | MediaTek Inc. |
| R1-2008977 | Enhancements to Multi-Beam Operations | Intel Corporation |
| R1-2009027 | Enhancements on multi-beam operation | Xiaomi |
| R1-2009060 | Discussion on Enhancements for Multi-beam Operation | Asia Pacific Telecom co. Ltd |
| R1-2009129 | Enhancements on multi-beam pperation | Sharp |
| R1-2009141 | Enhancements on Multi-beam Operation | Spreadtrum Communications |
| R1-2009155 | Discussion on multi-beam operation | ASUSTeK |
| R1-2009158 | Multi-beam Enhancements | Convida Wireless |
| R1-2009174 | Discussion on multi-beam operation | NTT DOCOMO, INC. |
| R1-2009250 | Enhancements on Multi-beam Operation | Qualcomm Incorporated |
| R1-2009288 | Enhancements on Multi-beam Operation | Ericsson |
| R1-2009499 | Moderator summary#2 for multi-beam enhancement | Moderator (Samsung) |
| R1-2009574 | Moderator summary#3 for multi-beam enhancement | Moderator (Samsung) |
| R1-2009715 | Moderator summary#4 for multi-beam enhancement | Moderator (Samsung) |
| R1-2009749 | Moderator summary#5 for multi-beam enhancement | Moderator (Samsung) |
| 8.1.2.1 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | |
| R1-2007540 | Multi-TRP/panel for non-PDSCH | FUTUREWEI |
| R1-2007587 | Enhancements on multi-TRP for reliability and robustness in Rel-17 | Huawei, HiSilicon |
| R1-2007627 | Reliability Enhancements for PDCCH, PUCCH, and PUSCH | InterDigital, Inc. |
| R1-2007645 | Further discussion on enhancement of MTRP operation | vivo |
| R1-2007764 | Multi-TRP enhancements for PDCCH, PUCCH and PUSCH | ZTE |
| R1-2007783 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Fujitsu |
| R1-2007793 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | TCL Communication Ltd. |
| R1-2007825 | Discussion on enhancements on multi-TRP/panel for PDCCH, PUCCH and PUSCH | CATT |
| R1-2008001 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | CMCC |
| R1-2008149 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Samsung |
| R1-2008218 | Enhancements on Multi-TRP based enhancement for PDCCH, PUCCH and PUSCH | OPPO |
| R1-2008347 | Considerations on Multi-TRP for PDCCH, PUCCH, PUSCH | Sony |
| R1-2008439 | Views on Rel-17 multi-TRP reliability enhancement | Apple |
| R1-2008574 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | LG Electronics |
| R1-2008898 | On multi-TRP enhancements for PDCCH and PUSCH | Fraunhofer IIS, Fraunhofer HHI |
| R1-2008904 | Enhancements for Multi-TRP URLLC schemes | Nokia, Nokia Shanghai Bell |
| R1-2008911 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Lenovo, Motorola Mobility |
| R1-2008944 | Discussion on multi-TRP for PDCCH, PUCCH and PUSCH | NEC |
| R1-2008958 | Enhancements on Multi-TRP for PDCCH, PUSCH and PUCCH | MediaTek Inc. |
| R1-2008978 | Multi-TRP enhancements for PDCCH, PUCCH and PUSCH | Intel Corporation |
| R1-2009028 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Xiaomi |
| R1-2009054 | Discussion on enhancements on multi-TRP for uplink channels | Asia Pacific Telecom co. Ltd |
| R1-2009130 | Enhancements on multi-TRP for PUSCH | Sharp |
| R1-2009142 | Discussion on enhancements on Multi-TRP for PDCCHPUCCH and PUSCH | Spreadtrum Communications |
| R1-2009159 | Multi-TRP Enhancements for PDCCH, PUCCH and PUSCH | Convida Wireless |
| R1-2009175 | Discussion on MTRP for reliability | NTT DOCOMO, INC. |
| R1-2009223 | On PDCCH, PUCCH and PUSCH enhancements with multiple TRPs | Ericsson |
| R1-2009251 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Qualcomm Incorporated |
| R1-2009284 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Qualcomm Incorporated |
| R1-2009480 | Summary of Multi-TRP URLLC for PUCCH and PUSCH | Moderator (Nokia, Nokia Shanghai Bell) |
| R1-2009683 | Summary of email discussions [103-e-NR-feMIMO-02] for mTRP PDCCH enhancements | Moderator (Qualcomm) |
| R1-2009757 | Summary of Multi-TRP URLLC for PUCCH and PUSCH | Moderator (Nokia, Nokia Shanghai Bell) |
| R1-2009761 | Summary#2 of email discussions [103-e-NR-feMIMO-02] for mTRP PDCCH enhancements | Moderator (Qualcomm) |
| R1-2009807 | LS on Beam switching gaps for Multi-TRP UL transmission | RAN1, Nokia |
| 8.1.2.2 | Enhancements on Multi-TRP inter-cell operation | |
| R1-2007541 | Inter-cell multi-TRP operation | FUTUREWEI |
| R1-2007588 | Enhancements on inter-cell multi-TRP operations in Rel-17 | Huawei, HiSilicon |
| R1-2007628 | Synchronization Analysis for M-TRP Inter-cell Operation | InterDigital, Inc. |
| R1-2007646 | Further discussion on inter-cell MTRP operation | vivo |
| R1-2007765 | Discussion on Multi-TRP inter-cell operation | ZTE |
| R1-2007826 | Discussion on multi-TRP/panel inter-cell operation | CATT |
| R1-2008002 | Enhancements on Multi-TRP inter-cell operation | CMCC |
| R1-2008150 | Enhancements on Multi-TRP inter-cell operation | Samsung |
| R1-2008219 | Enhancement on inter-cell multi-TRP operation | OPPO |
| R1-2008348 | Considerations on inter-cell operation | Sony |
| R1-2008440 | Views on Rel-17 Inter-cell multi-TRP operation | Apple |
| R1-2008575 | Enhancements on Multi-TRP inter-cell operation | LG Electronics |
| R1-2008905 | Enhancements to enable inter-cell multi-TRP operations | Nokia, Nokia Shanghai Bell |
| R1-2008912 | Enhancements on Multi-TRP inter-cell operation | Lenovo, Motorola Mobility |
| R1-2008945 | Discussion on multi-TRP inter-cell operation | NEC |
| R1-2008979 | Multi-TRP enhancements for inter-cell operation | Intel Corporation |
| R1-2009029 | Enhancement on Inter-cell Multi-TRP operations | Xiaomi |
| R1-2009070 | Enhancement on Multi-TRP inter-cell operation | Ericsson |
| R1-2009143 | Discussion on enhancement on multi-TRP inter-cell operation | Spreadtrum Communications |
| R1-2009176 | Discussion on inter-cell multi-TRP operations | NTT DOCOMO, INC. |
| R1-2009252 | Enhancements on Multi-TRP inter-cell operation | Qualcomm Incorporated |
| R1-2009415 | FL summary on inter-cell MTRP operation | Moderator (vivo) |
| R1-2009731 | FL summary#2 on inter-cell MTRP operation | Moderator (vivo) |
| 8.1.2.3 | Enhancements on beam management for multi-TRP | |
| R1-2007542 | Beam management for simultaneous multi-TRP transmission with multi-panel reception | FUTUREWEI |
| R1-2007589 | Discussion on multi-TRP for multi-panel reception in Rel-17 | Huawei, HiSilicon |
| R1-2007629 | Beam Management Enhancements for Multi-TRP | InterDigital, Inc. |
| R1-2007647 | Further discussion on MTRP multibeam enhancement | vivo |
| R1-2007766 | Enhancements on beam management for Multi-TRP | ZTE |
| R1-2007784 | Enhancements on beam management for multi-TRP | Fujitsu |
| R1-2007827 | Beam management enhancement for multi-TRP simultaneous reception | CATT |
| R1-2008003 | Enhancements on beam management for multi-TRP | CMCC |
| R1-2008151 | Enhancements on beam management for multi-TRP | Samsung |
| R1-2008220 | Enhancements on beam management for multi-TRP | OPPO |
| R1-2008309 | Enhancements on beam management for multi-TRP | AT&T |
| R1-2008349 | Considerations on beam management for multi-TRP | Sony |
| R1-2008441 | Views on Rel-17 multi-TRP BM enhancement | Apple |
| R1-2008576 | Enhancements on beam management for multi-TRP | LG Electronics |
| R1-2008906 | Enhancements on Beam Management for Multi-TRP/Panel Transmission | Nokia, Nokia Shanghai Bell |
| R1-2008913 | Enhancements on beam management for multi-TRP | Lenovo, Motorola Mobility |
| R1-2008946 | Discussion on beam management for multi-TRP | NEC |
| R1-2008957 | Enhancements on beam management for multi-TRP | MediaTek Inc. |
| R1-2008980 | Multi-TRP enhancements for beam management | Intel Corporation |
| R1-2009030 | Enhancement on beam management for Multi-TRP | Xiaomi |
| R1-2009052 | Discussion of enhancements on beam management for multi-TRP | Asia Pacific Telecom co. Ltd |
| R1-2009144 | Discussion on enhancements on beam management for multi-TRP | Spreadtrum Communications |
| R1-2009156 | Discussion on beam management for multi-TRP | ASUSTeK |
| R1-2009160 | On Per-TRP Beam Failure Recovery | Convida Wireless |
| R1-2009177 | Discussion on beam management for MTRP | NTT DOCOMO, INC. |
| R1-2009213 | Discussion on beam management for multi-TRP | ITRI |
| R1-2009225 | On beam management enhancements for simultaneous multi-TRP transmission with multi-panel reception | Ericsson |
| R1-2009253 | Enhancements on beam management for multi-TRP | Qualcomm Incorporated |
| R1-2009500 | Moderator summary on beam management enhancement for M-TRP | Moderator (CATT) |
| R1-2009728 | Moderator summary on round#3 discussion on M-TRP beam management | Moderator (CATT) |
| 8.1.2.4 | Enhancements on HST-SFN deployment | |
| R1-2007543 | Enhancement to support HST-SFN deployment scenario | FUTUREWEI |
| R1-2007590 | Discussion on multi-TRP for high speed train in Rel-17 | Huawei, HiSilicon |
| R1-2007630 | Enhancements for M-TRP to Support HST-SFN Deployment | InterDigital, Inc. |
| R1-2007648 | Further discussion and evaluation on HST-SFN schemes | vivo |
| R1-2007767 | Discussion on Multi-TRP HST enhancements | ZTE |
| R1-2007828 | On enhancements on HST-SFN deployment | CATT |
| R1-2008004 | Enhancements on HST-SFN deployment | CMCC |
| R1-2008152 | Enhancements on HST-SFN | Samsung |
| R1-2008221 | Enhancements on HST-SFN deployment | OPPO |
| R1-2008350 | Considerations on HST-SFN operation for multi-TRP | Sony |
| R1-2008442 | Views on Rel-17 HST enhancement | Apple |
| R1-2008577 | Enhancements on HST-SFN deployment | LG Electronics |
| R1-2008907 | Enhancements for HST-SFN deployment | Nokia, Nokia Shanghai Bell |
| R1-2008947 | Discussion on HST-SFN deployment | NEC |
| R1-2008981 | Enhancements to HST-SFN deployments | Intel Corporation |
| R1-2009069 | Enhancement on HST-SFN deployment | Ericsson |
| R1-2009099 | Enhancements for HST-SFN deployment | Lenovo, Motorola Mobility |
| R1-2009145 | Discussion on enhancements on HST-SFN deployment | Spreadtrum Communications |
| R1-2009178 | Discussion on HST-SFN deployment | NTT DOCOMO, INC. |
| R1-2009254 | Enhancements on HST-SFN deployment | Qualcomm Incorporated |
| R1-2009476 | Summary#1 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2009523 | Enhancement on HST-SFN deployment | Ericsson |
| R1-2009557 | Enhancement on HST-SFN deployment | Ericsson |
| R1-2009646 | Summary#2 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2009750 | Summary#3 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| 8.1.3 | Enhancements on SRS flexibility, coverage and capacity | |
| R1-2007544 | Enhancements on SRS flexibility, coverage and capacity | FUTUREWEI |
| R1-2007591 | Discussion on SRS enhancements for Rel-17 | Huawei, HiSilicon |
| R1-2007631 | Discussion on SRS Enhancements | InterDigital, Inc. |
| R1-2007649 | Further discussion on SRS enhancement | vivo |
| R1-2007768 | Enhancements on SRS flexibility, coverage and capacity | ZTE |
| R1-2007829 | On enhancements on SRS flexibility, coverage and capacity | CATT |
| R1-2008005 | Enhancements on SRS flexibility, coverage and capacity | CMCC |
| R1-2008153 | Enhancements on SRS | Samsung |
| R1-2008222 | Enhancements on SRS flexibility, coverage and capacity | OPPO |
| R1-2008351 | Considerations on SRS flexibility, coverage and capacity | Sony |
| R1-2008443 | Views on Rel-17 SRS enhancement | Apple |
| R1-2008578 | Enhancements on SRS flexibility, coverage and capacity | LG Electronics |
| R1-2008900 | Enhancements on SRS for coverage and capacity | Fraunhofer IIS, Fraunhofer HHI |
| R1-2008908 | Enhancements on SRS flexibility, coverage and capacity | Nokia, Nokia Shanghai Bell |
| R1-2008914 | Enhancements on SRS | Lenovo, Motorola Mobility |
| R1-2008948 | Discussion on SRS enhancement | NEC |
| R1-2008959 | Enhancements on SRS flexibility, coverage and capacity | MediaTek Inc. |
| R1-2008982 | Discussion on SRS enhancements | Intel Corporation |
| R1-2009031 | Discussion on SRS enhancements | Xiaomi |
| R1-2009131 | Enhancements on SRS | Sharp |
| R1-2009146 | Considerations on SRS enhancement | Spreadtrum Communications |
| R1-2009179 | Discussion on SRS enhancement | NTT DOCOMO, INC. |
| R1-2009211 | SRS Performance and Potential Enhancements | Ericsson LM |
| R1-2009255 | Enhancements on SRS flexibility, coverage and capacity | Qualcomm Incorporated |
| R1-2009286 | Discussion on enhancement of SRS in Rel. 17 further enhanced MIMO | CEWiT |
| R1-2009384 | FL summary #1 on SRS enhancements | Moderator (ZTE) |
| R1-2009421 | Enhancements on SRS flexibility, coverage and capacity | Nokia, Nokia Shanghai Bell |
| R1-2009650 | FL summary #2 on SRS enhancements | Moderator (ZTE) |
| R1-2009723 | FL summary #3 on SRS enhancements | Moderator (ZTE) |
| 8.1.4 | CSI enhancements: MTRP and FR1 FDD reciprocity | |
| R1-2007545 | CSI enhancement for multi-TRP and FDD | FUTUREWEI |
| R1-2007592 | Discussion on CSI Enhancements for Rel-17 | Huawei, HiSilicon |
| R1-2007632 | CSI Enhancements for the Support of MTRP and FDD Reciprocity | InterDigital, Inc. |
| R1-2007650 | Further discussion and evaluation on MTRP CSI and Partial reciprocity | vivo |
| R1-2007769 | CSI enhancements for Multi-TRP and FR1 FDD reciprocity | ZTE |
| R1-2007830 | CSI enhancements for MTRP and FR1 FDD with partial reciprocity | CATT |
| R1-2008006 | Enhancements on CSI reporting for Multi-TRP | CMCC |
| R1-2008154 | Views on Rel. 17 CSI enhancements | Samsung |
| R1-2008223 | CSI enhancement for M-TRP and FDD reciprocity | OPPO |
| R1-2008352 | Considerations on CSI enhancements | Sony |
| R1-2008444 | Views on Rel-17 CSI enhancement | Apple |
| R1-2008579 | CSI enhancements for Rel-17 | LG Electronics |
| R1-2008901 | CSI enhancements on Type II PS codebook and multi-TRP | Fraunhofer IIS, Fraunhofer HHI |
| R1-2008909 | Enhancement on CSI measurement and reporting | Nokia, Nokia Shanghai Bell |
| R1-2008949 | Discussion on CSI enhancement for multi-TRP | NEC |
| R1-2008960 | CSI enhancement for NCJT | MediaTek Inc. |
| R1-2008983 | On CSI enhancements for MTRP and FDD reciprocity | Intel Corporation |
| R1-2009100 | CSI enhancements for mTRP and FDD reciprocity | Lenovo, Motorola Mobility |
| R1-2009147 | Discussion on CSI enhancement for M-TRP transmission and FR1 FDD reciprocity | Spreadtrum Communications |
| R1-2009180 | Discussion on CSI enhancements | NTT DOCOMO, INC. |
| R1-2009224 | On CSI enhancements in Rel-17 feMIMO | Ericsson |
| R1-2009256 | CSI enhancements - MTRP and FR1 FDD reciprocity | Qualcomm Incorporated |
| R1-2009416 | On CSI enhancements for MTRP and FDD reciprocity | Intel Corporation |
| R1-2009452 | On CSI enhancements for MTRP and FDD reciprocity | Intel Corporation |
| R1-2009495 | Further discussion and evaluation on MTRP CSI and Partial reciprocity | vivo |
| R1-2009509 | Further discussion and evaluation on MTRP CSI and Partial reciprocity | vivo |
| R1-2009529 | Summary of CSI enhancements for MTRP and FDD | Moderator (Huawei) |
| R1-2009530 | Summary of Further Email discussion for Rel-17 CSI enhancements | Moderator (Huawei) |
| R1-2009759 | Summary of Phase 3 Email discussion for Rel-17 CSI enhancements | Moderator (Huawei) |
| 8.1.5 | Other | |
| R1-2007547 | Sounding enhancement for interference probing in TDD massive MIMO | FUTUREWEI |
| R1-2007633 | Updated Results on Multi-TRP MIMO Deployments with Multi-Panel UEs | InterDigital, Inc. |
| R1-2007651 | Discussion on higher layer aspects for multi-TRP enhancement | vivo |
| R1-2007770 | Further details on Multi-beam and Multi-TRP operation | ZTE |
| R1-2007831 | Evaluation of multi-TRP enhancement | CATT |
| R1-2008155 | Simulation results for multi-beam enhancements | Samsung |
| R1-2008323 | Discussion on field measurement and evaluation assumptions for FDD CSI enhancements in Rel-17 | Huawei, HiSilicon |
| R1-2008755 | Analysis of Control Signaling for multi-beam operation | Dongguan OPPO Precision Elec. |
| R1-2008902 | On FDD channel reciprocity in real-world scenarios | Fraunhofer IIS, Fraunhofer HHI |
| R1-2008915 | HARQ feedback of SPS PDSCH reception in multi-DCI based multiple TRPs | Lenovo, Motorola Mobility |
| R1-2009010 | Evaluation of multi-TRP transmission with multi-panel reception | ETRI |
| R1-2009132 | Other enhancements for beam management. | Sharp |
| R1-2009181 | Discussion on UL dense deployment | NTT DOCOMO, INC. |
| R1-2009290 | Additional simulation results on multi-beam operation | Ericsson |
| R1-2009367 | Simulation results for multi-beam enhancements | Samsung |
| 8.2 | Study on supporting NR from 52.6GHz to 71 GHz | |
| R1-2007958 | Draft TR 38.808 v002: Study on supporting NR from 52.6 GHz to 71 GHz | Rapporteur (Intel Corporation) |
| R1-2009713 | TR 38.808 v010: Study on supporting NR from 52.6 GHz to 71 GHz | Rapporteur (Intel Corporation) |
| R1-2009833 | Session notes for 8.2 (Study on supporting NR from 52.6 GHz to 71 GHz) | Ad-Hoc Chair (Ericsson) |
| R1-2009849 | TR 38.808 v020: Study on supporting NR from 52.6 GHz to 71 GHz | Rapporteur (Intel Corporation) |
| 8.2.1 | Required changes to NR using existing DL/UL NR waveform | |
| R1-2007549 | Further discussion on B52 numerology | FUTUREWEI |
| R1-2007558 | Discussion on physical layer impacts for NR beyond 52.6 GHz | Lenovo, Motorola Mobility |
| R1-2007604 | PHY design in 52.6-71 GHz using NR waveform | Huawei, HiSilicon |
| R1-2007642 | Physical layer design for NR 52.6-71GHz | Beijing Xiaomi Software Tech |
| R1-2007652 | Discussion on requried changes to NR using existing DL/UL NR waveform | vivo |
| R1-2007785 | Consideration on required changes to NR using existing NR waveform | Fujitsu |
| R1-2007790 | Consideration on supporting above 52.6GHz in NR | InterDigital, Inc. |
| R1-2007847 | System Analysis of NR opration in 52.6 to 71 GHz | CATT |
| R1-2007883 | Required changes to NR using existing DL/UL NR waveform | TCL Communication Ltd. |
| R1-2007926 | Required changes to NR using existing DL/UL NR waveform | Nokia, Nokia Shanghai Bell |
| R1-2007929 | On phase noise compensation for NR from 52.6GHz to 71GHz | Mitsubishi Electric RCE |
| R1-2007941 | Discussion on Required Changes to NR in 52.6 – 71 GHz | Intel Corporation |
| R1-2007965 | On the required changes to NR for above 52.6GHz | ZTE, Sanechips |
| R1-2007982 | On NR operations in 52.6 to 71 GHz | Ericsson |
| R1-2008045 | Consideration on required physical layer changes to support NR above 52.6 GHz | LG Electronics |
| R1-2008076 | Discussion on required changes to NR using existing DL/UL NR waveform in 52.6GHz ~ 71GHz | CMCC |
| R1-2008082 | Study on the numerology to support 52.6 GHz to 71GHz | NEC |
| R1-2008156 | Design aspects for extending NR to up to 71 GHz | Samsung |
| R1-2008250 | Discusson on required changes to NR using DL/UL NR waveform | OPPO |
| R1-2008353 | Considerations on required changes to NR from 52.6 GHz to 71 GHz | Sony |
| R1-2008457 | A Discussion on Physical Layer Design for NR above 52.6GHz | Apple |
| R1-2008493 | Discussions on required changes on supporting NR from 52.6GHz to 71 GHz | CAICT |
| R1-2008501 | On required changes to NR using existing DL/UL NR waveform for operation in 60GHz band | MediaTek Inc. |
| R1-2008516 | On NR operation between 52.6 GHz and 71 GHz | Convida Wireless |
| R1-2008547 | Evaluation Methodology and Required Changes on NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2008615 | NR using existing DL-UL NR waveform to support operation between 52p6 GHz and 71 GHz | Qualcomm Incorporated |
| R1-2008726 | Discussion on physical layer aspects for NR beyond 52.6GHz | WILUS Inc. |
| R1-2008769 | Waveform considerations for NR above 52.6 GHz | Charter Communications |
| R1-2008805 | Discussion on Required Changes to NR in 52.6 – 71 GHz | Intel Corporation |
| R1-2008872 | Design aspects for extending NR to up to 71 GHz | Samsung |
| R1-2009062 | Evaluation Methodology and Required Changes on NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2009313 | Issue Summary for physical layer changes for supporting NR from 52.6 GHz to 71 GHz | Moderator (Intel Corporation) |
| R1-2009352 | [103-e-NR-52-71-Waveform-Changes] Discussions Summary #1 | Moderator (Intel Corporation) |
| R1-2009379 | Discussion on Required Changes to NR in 52.6 – 71 GHz | Intel Corporation |
| R1-2009403 | [103-e-NR-52-71-Waveform-Changes] Discussions Summary #1 | Moderator (Intel Corporation) |
| R1-2009540 | [103-e-NR-52-71-Waveform-Changes] Discussions Summary #2 | Moderator (Intel Corporation) |
| R1-2009653 | Consideration on required physical layer changes to support NR above 52.6 GHz | LG Electronics |
| R1-2009667 | [103-e-NR-52-71-Waveform-Changes] Discussions Summary #3 | Moderator (Intel Corporation) |
| R1-2009668 | Summary of 38.808 TR Text Proposal Discussion | Moderator (Intel Corporation) |
| R1-2009688 | [103-e-NR-52-71-Waveform-Changes] Discussions Summary #4 | Moderator (Intel Corporation) |
| R1-2009717 | [103-e-NR-52-71-Waveform-Changes] Discussions Summary #5 | Moderator (Intel Corporation) |
| R1-2009718 | [103-e-NR-52-71-Waveform-Changes] Discussions Summary #6 | Moderator (Intel Corporation) |
| R1-2009779 | Summary#2 of 38.808 TR Text Proposal Discussion | Moderator (Intel Corporation) |
| 8.2.2 | Channel access mechanism | |
| R1-2007550 | On channel access modes in 60GHz | FUTUREWEI |
| R1-2007559 | Discussion on channel access for NR beyond 52.6 GHz | Lenovo, Motorola Mobility |
| R1-2007605 | Channel access mechanism for 60 GHz unlicensed operation | Huawei, HiSilicon |
| R1-2007643 | Channel access mechanism for NR on 52.6-71 GHz | Beijing Xiaomi Software Tech |
| R1-2007653 | Discussion on channel access mechanism | vivo |
| R1-2007791 | On Channel access mechanisms | InterDigital, Inc. |
| R1-2007848 | Channel Access Mechanism in support of NR operation in 52.6 to 71 GHz | CATT |
| R1-2007884 | Channel access mechanism | TCL Communication Ltd. |
| R1-2007918 | Channel access mechanisms for NR from 52.6-71GHz | AT&T |
| R1-2007927 | Design of NR channel access mechanisms for 60 GHz unlicensed band | Nokia, Nokia Shanghai Bell |
| R1-2007942 | Channel Access Procedure for NR in 52.6 - 71 GHz | Intel Corporation |
| R1-2007966 | On the channel access mechanism for above 52.6GHz | ZTE, Sanechips |
| R1-2007983 | Channel Access Mechanism | Ericsson |
| R1-2008046 | Considerations on channel access mechanism to support NR above 52.6 GHz | LG Electronics |
| R1-2008091 | Discussion on channel access mechanism for above 52.6GHz | Spreadtrum Communications |
| R1-2008157 | Channel access mechanism for 60 GHz unlicensed spectrum | Samsung |
| R1-2008251 | Discussion on channel access | OPPO |
| R1-2008354 | Channel access mechanism for 60 GHz unlicensed spectrum | Sony |
| R1-2008458 | Views on Channel Access Mechanisms for Unlicensed Access above 52.6 GHz | Apple |
| R1-2008494 | Discussions on channel access mechanism on supporting NR from 52.6GHz to 71 GHz | CAICT |
| R1-2008517 | On Channel Access Mechanism and Interference Handling for Supporting NR from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2008548 | Channel Access Mechanism for NR in 60 GHz unlicensed spectrum | NTT DOCOMO, INC. |
| R1-2008563 | Discussion on channel access mechanism | ITRI |
| R1-2008616 | Channel access mechanism for NR in 52p6 to 71GHz band | Qualcomm Incorporated |
| R1-2008630 | Channel access mechanism for NR in 52p6 to 71GHz band | Qualcomm Incorporated |
| R1-2008717 | Discussion on channel access mechanism for 52.6 to 71GHz unlicensed band | Potevio |
| R1-2008770 | Further aspects of channel access mechanisms | Charter Communications |
| R1-2008806 | Channel Access Procedure for NR in 52.6 - 71 GHz | Intel Corporation |
| R1-2008889 | Channel access mechanism for NR in 52p6 to 71GHz band | Qualcomm Incorporated |
| R1-2008976 | Channel access mechanism for 60 GHz unlicensed operation | Huawei, HiSilicon |
| R1-2009312 | Design of NR channel access mechanisms for 60 GHz unlicensed band | Nokia, Nokia Shanghai Bell |
| R1-2009344 | FL summary for channel access of 52.6GHz to 71GHz band | Moderator (Qualcomm) |
| R1-2009362 | Channel access mechanism for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2009363 | FL summary#2 for channel access of 52.6GHz to 71GHz band | Moderator (Qualcomm) |
| R1-2009368 | FL summary#3 for channel access of 52.6GHz to 71GHz band | Moderator (Qualcomm) |
| R1-2009380 | Channel Access Procedure for NR in 52.6 - 71 GHz | Intel Corporation |
| R1-2009408 | FL summary#4 for channel access of 52.6GHz to 71GHz band | Moderator (Qualcomm) |
| R1-2009521 | FL summary#5 for channel access of 52.6GHz to 71GHz band | Moderator (Qualcomm) |
| R1-2009572 | FL summary#6 for channel access of 52.6GHz to 71GHz band | Moderator (Qualcomm) |
| R1-2009626 | FL summary#7 for channel access of 52.6GHz to 71GHz band | Moderator (Qualcomm) |
| R1-2009675 | FL summary#8 for channel access of 52.6GHz to 71GHz band | Moderator (Qualcomm) |
| R1-2009724 | FL summary#9 for channel access of 52.6GHz to 71GHz band | Moderator (Qualcomm) |
| R1-2009760 | FL summary#10 for channel access of 52.6GHz to 71GHz band | Moderator (Qualcomm) |
| 8.2.3 | Other | |
| R1-2007560 | Additional evaluations for NR beyond 52.6GHz | Lenovo, Motorola Mobility |
| R1-2007654 | Evaluation on different numerologies for NR using existing DL/UL NR waveform | vivo |
| R1-2007792 | Evaluation results for above 52.6 GHz | InterDigital, Inc. |
| R1-2007928 | Simulation Results for NR from 52.6 GHz to 71 GHz | Nokia, Nokia Shanghai Bell |
| R1-2007943 | Considerations on performance evaluation for NR in 52.6-71GHz | Intel Corporation |
| R1-2007967 | Simulation results for NR above 52.6GHz | ZTE, Sanechips |
| R1-2007984 | Evaluation results for NR in 52.6 - 71 GHz | Ericsson |
| R1-2008047 | Considerations on phase noise compensation to support NR above 52.6 GHz | LG Electronics |
| R1-2008158 | Evaluaton results for extending NR to up to 71 GHz | Samsung |
| R1-2008252 | Discussion on other aspects | OPPO |
| R1-2008459 | Evaluation results for Physical Layer Design for NR above 52.6GHz | Apple |
| R1-2008549 | Potential Enhancements for NR on 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2008771 | Performance evaluations for NR above 52.6 GHz | Charter Communications |
| R1-2008779 | Link level and System level evaluation for NR system operating in 52.6GHz to 71GHz | Huawei, HiSilicon |
| R1-2008873 | Evaluaton results for extending NR to up to 71 GHz | Samsung |
| R1-2008890 | FL Summary of system level evaluation results for NR from 52.6GHz to 71GHz | Moderator (Qualcomm) |
| R1-2009111 | Summary of link level evaluation results and related issues on supporting NR from 52.6 GHz to 71 GHz | Moderator (vivo) |
| R1-2009157 | Performance evaluations for NR above 52.6 GHz | Charter Communications, Inc |
| R1-2009355 | Discussion summary #1 for [103-e-NR-52-71-Evaluations] | Moderator (vivo) |
| R1-2009356 | Collection of evaluation results on supporting NR from 52.6 GHz to 71 GHz | Moderator (vivo, Qualcomm) |
| R1-2009377 | Discussion summary #2 for [103-e-NR-52-71-Evaluations] | Moderator (vivo) |
| R1-2009392 | Discussion summary #3 for [103-e-NR-52-71-Evaluations] | Moderator (vivo) |
| R1-2009450 | Simulation results for NR above 52.6GHz | ZTE, Sanechips |
| R1-2009459 | Link level and System level evaluation for NR system operating in 52.6GHz to 71GHz | Huawei, HiSilicon |
| R1-2009524 | Discussion summary #4 for [103-e-NR-52-71-Evaluations] | Moderator (vivo) |
| R1-2009609 | Discussion summary #5 for [103-e-NR-52-71-Evaluations] | Moderator (vivo) |
| R1-2009610 | Link level and System level evaluation for NR system operating in 52.6GHz to 71GHz | Huawei, HiSilicon |
| R1-2009615 | Discussion on other aspects | OPPO |
| 8.3.1.1 | UE feedback enhancements for HARQ-ACK | |
| R1-2007565 | UE feedback enhancements for HARQ-ACK | Huawei, HiSilicon |
| R1-2007655 | HARQ-ACK enahncements for Rel-17 URLLC | vivo |
| R1-2007707 | HARQ-ACK Enhancements for IIoT/URLLC | Ericsson |
| R1-2007789 | UE feedback enhancements for HARQ-ACK | TCL Communication Ltd. |
| R1-2007849 | UE feedback enhancements for HARQ-ACK | CATT |
| R1-2007900 | HARQ feedback enhancement for URLLC | Beijing Xiaomi Software Tech |
| R1-2008007 | Discussion on UE feedback enhancements for HARQ-ACK | CMCC |
| R1-2008057 | Discussion on UE feedback enhancement for HARQ-ACK | LG Electronics |
| R1-2008159 | HARQ-ACK feedback enhancements for Rel-17 URLLC/IIoT | Samsung |
| R1-2008279 | HARQ-ACK enhancements for Rel-17 URLLC/IIoT | OPPO |
| R1-2008355 | Considerations in HARQ-ACK enhancements for URLLC | Sony |
| R1-2008460 | Discussion on UE feedback enhancements for HARQ-ACK | Apple |
| R1-2008821 | Discussion on HARQ-ACK enhancements for eURLLC | ZTE |
| R1-2008842 | HARQ-ACK Feedback Enhancements for URLLC/IIoT | Nokia, Nokia Shanghai Bell |
| R1-2008941 | UE feedback enhancements for HARQ-ACK | NEC Corporation |
| R1-2008952 | Discussion on UE feedback enhancements for HARQ-ACK | Panasonic Corporation |
| R1-2008984 | Discussion on prioritized UE HARQ feedback enhancements for URLLC/IIoT | Intel Corporation |
| R1-2009011 | UE feedback enhancements for HARQ-ACK | ETRI |
| R1-2009053 | Discussion on UE feedback enhancements for HARQ-ACK | Asia Pacific Telecom co. Ltd |
| R1-2009063 | On UE feedback enhancements for HARQ-ACK | MediaTek Inc. |
| R1-2009083 | HARQ-ACK enhancements for DL SPS | InterDigital, Inc. |
| R1-2009101 | HARQ-ACK feedback enhancement for IIoT/URLLC | Lenovo, Motorola Mobility |
| R1-2009133 | UE feedback enhancements for HARQ-ACK | Sharp |
| R1-2009140 | UE feedback enhancements for HARQ-ACK | China Unicom |
| R1-2009148 | Discussion on necessity and support of Physical Layer feedback enhancements | Spreadtrum Communications |
| R1-2009182 | Discussion on HARQ-ACK feedback enhancements for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2009246 | Discussion on HARQ-ACK enhancement for URLLC/IIoT | WILUS Inc. |
| R1-2009257 | HARQ-ACK enhancement for IOT and URLLC | Qualcomm Incorporated |
| R1-2009566 | Moderator summary #1 on Rel-17 HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT (AI 8.3.1.1) | Moderator (Nokia) |
| R1-2009789 | Moderator summary on Rel-17 HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT (AI 8.3.1.1) – end of meeting | Moderator (Nokia) |
| 8.3.1.2 | CSI feedback enhancements | |
| R1-2007539 | CSI feedback enhancements for URLLC | FUTUREWEI |
| R1-2007566 | CSI feedback enhancements | Huawei, HiSilicon |
| R1-2007656 | CSI feedback enhancements for Rel-17 URLLC | vivo |
| R1-2007708 | CSI Feedback Enhancements for IIoT/URLLC | Ericsson |
| R1-2007850 | CSI feedback enhancements | CATT |
| R1-2008008 | Discussion on CSI feedback enhancements | CMCC |
| R1-2008058 | Discussion on CSI feedback enhancements for URLLC | LG Electronics |
| R1-2008107 | Discussion on CSI feedback enhancements | Spreadtrum Communications |
| R1-2008160 | CSI feedback enhancements for URLLC | Samsung |
| R1-2008280 | CSI feedback enhancements for URLLC | OPPO |
| R1-2008356 | Considerations in CSI feedback enhancements | Sony |
| R1-2008461 | Discussion on CSI feedback enhancements for URLLC/IIoT | Apple |
| R1-2008495 | CSI Feedback Enhancements for IIoT/URLLC | III |
| R1-2008822 | Discussion on CSI feedback enhancements for eURLLC | ZTE |
| R1-2008847 | CSI feedback enhancement | NEC |
| R1-2008862 | CSI feedback enhancements for URLLC/IIoT use cases | Nokia, Nokia Shanghai Bell |
| R1-2008936 | CSI feedback enhancements for enhanced URLLC/IIoT | InterDigital, Inc. |
| R1-2008953 | Discussion on CSI feedback enhancements | Panasonic Corporation |
| R1-2008985 | Discussion on prioritized CSI feedback enhancements for URLLC/IIoT | Intel Corporation |
| R1-2009064 | CSI feedback enhancements for URLLC | MediaTek Inc. |
| R1-2009102 | CSI feedback enhancements for URLLC/IIoT | Lenovo, Motorola Mobility |
| R1-2009134 | CSI feedback enhancements for eURLLC | Sharp, NICT |
| R1-2009183 | Discussion on CSI feedback enhancements for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2009258 | CSI enhancement for IOT and URLLC | Qualcomm Incorporated |
| R1-2009455 | Feature lead summary #1 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital, Inc.) |
| R1-2009558 | Feature lead summary #2 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital, Inc.) |
| R1-2009649 | Feature lead summary #3 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital, Inc.) |
| R1-2009768 | Discussion on CSI feedback enhancements for URLLC/IIoT | Apple |
| R1-2009775 | Feature lead summary #4 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital, Inc.) |
| 8.3.2 | Enhancements for unlicensed band URLLC/IIoT | |
| R1-2007551 | UE initiated COT for FFP | FUTUREWEI |
| R1-2007568 | Uplink enhancements for URLLC in unlicensed controlled environments | Huawei, HiSilicon |
| R1-2007657 | Enhancements for unlicensed band URLLC/IIoT | vivo |
| R1-2007709 | Enhancements for IIoT/URLLC on Unlicensed Band | Ericsson |
| R1-2007851 | Enhancements for unlicensed band URLLC/IIoT | CATT |
| R1-2007885 | Enhancements for unlicensed band URLLC/IIoT | TCL Communication Ltd. |
| R1-2007902 | Enhancement for unlicensed band URLLC IIoT | Beijing Xiaomi Software Tech |
| R1-2008059 | Discussion on unlicensed band URLLC/IIOT | LG Electronics |
| R1-2008108 | Discussion on enhancements for unlicensed band URLLCIIoT | Spreadtrum Communications |
| R1-2008161 | Enhancements for unlicensed band URLLC/IIoT | Samsung |
| R1-2008281 | Enhancements for unlicensed band URLLC/IIoT | OPPO |
| R1-2008357 | Considerations in unlicensed URLLC | Sony |
| R1-2008462 | URLLC uplink enhancements for unlicensed spectrum | Apple |
| R1-2008568 | UL enhancements for IIoT/URLLC in unlicensed controlled environment | Nokia, Nokia Shanghai Bell |
| R1-2008823 | Discussion on unlicensed band URLLC/IIoT | ZTE |
| R1-2008834 | Unlicensed aspects for IIoT | Charter Communications |
| R1-2008891 | Enhancements for unlicensed band URLLC/IIoT | NEC |
| R1-2008954 | Enhancements for unlicensed band URLLC/IIoT | Panasonic Corporation |
| R1-2008986 | Enhancements to Enable URLLC/IIoT in Unlicensed Band | Intel Corporation |
| R1-2009012 | Enhancements for unlicensed band URLLC/IIoT | ETRI |
| R1-2009065 | On the enhancements for unlicensed band URLLC/IIoT | MediaTek Inc. |
| R1-2009084 | Enhancements for unlicensed band URLLC/IIoT | InterDigital, Inc. |
| R1-2009103 | Enhancements for unlicensed band URLLC/IIoT | Lenovo, Motorola Mobility |
| R1-2009135 | Enhancements for unlicensed band URLLC/IIoT | Sharp |
| R1-2009184 | Discussion on enhancements for unlicensed band URLLC | NTT DOCOMO, INC. |
| R1-2009247 | Discussion on enhancement for unlicensed URLLC/IIoT | WILUS Inc. |
| R1-2009259 | Uplink enhancements for URLLC in unlicensed controlled environments | Qualcomm Incorporated |
| R1-2009492 | Summary#1 on Enhancements for URLLC/IIoT on Unlicensed Band | Moderator (Ericsson) |
| R1-2009601 | Summary#2 on Enhancements for URLLC/IIoT on Unlicensed Band | Moderator (Ericsson) |
| R1-2009710 | Summary#3 on Enhancements for URLLC/IIoT on Unlicensed Band | Moderator (Ericsson) |
| R1-2009781 | Summary#4 on Enhancements for URLLC/IIoT on Unlicensed Band | Moderator (Ericsson) |
| 8.3.3 | Intra-UE Multiplexing/Prioritization | |
| R1-2007567 | Intra-UE multiplexing enhancements | Huawei, HiSilicon |
| R1-2007658 | Intra-UE Multiplexing/Prioritization for Rel-17 URLLC | vivo |
| R1-2007710 | Intra-UE Multiplexing/Prioritization Enhancements for IIoT/URLLC | Ericsson |
| R1-2007852 | Intra-UE multiplexing and prioritization | CATT |
| R1-2007901 | Intra-UE multiplexing prioritization | Beijing Xiaomi Software Tech |
| R1-2008009 | Discussion on intra-UE multiplexing/prioritization | CMCC |
| R1-2008060 | Discussion on Intra-UE multiplexing/prioritization | LG Electronics |
| R1-2008162 | Uplink intra-UE multiplexing and prioritization | Samsung |
| R1-2008282 | Enhancements on intra-UE multiplexing/prioritization | OPPO |
| R1-2008358 | Considerations in intra-UE UL multiplexing | Sony |
| R1-2008463 | Discussion on Intra-UE Multiplexing/Prioritization | Apple |
| R1-2008824 | Discussion on enhanced intra-UE multiplexing | ZTE |
| R1-2008843 | On UL intra-UE prioritization and multiplexing enhancements | Nokia, Nokia Shanghai Bell |
| R1-2008848 | Discussion on Intra-UE prioritization and multiplexing | NEC |
| R1-2008937 | Intra-UE multiplexing and prioritization | InterDigital, Inc. |
| R1-2008955 | Discussion on Intra-UE multiplexing and prioritization of different priority | Panasonic Corporation |
| R1-2008987 | On Intra-UE Multiplexing and Prioritization for Release 17 URLLC/IIoT | Intel Corporation |
| R1-2009013 | Intra-UE Multiplexing/Prioritization | ETRI |
| R1-2009045 | Summary#1 on Intra-UE Multiplexing/Prioritization for R17 | OPPO |
| R1-2009066 | Methods for intra-UE multiplexing and prioritization | MediaTek Inc. |
| R1-2009104 | Intra-UE multiplexing enhancement for IIoT/URLLC | Lenovo, Motorola Mobility |
| R1-2009136 | Enhancements on intra-UE UCI multiplexing and PUSCH prioritization | Sharp |
| R1-2009149 | Discussion on intra-UE multiplexing/prioritization | Spreadtrum Communications |
| R1-2009185 | Discussion on intra-UE multiplexing/prioritization for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2009214 | Discussion on intra-UE multiplexing | ITRI |
| R1-2009248 | Discussion on Intra-UE multiplexing/prioritization for URLLC/IIoT | WILUS Inc. |
| R1-2009260 | Intra-UE multiplexing and prioritization for IOT and URLLC | Qualcomm Incorporated |
| R1-2009546 | Summary#1 of email thread [103-e-NR-IIOT_URLLC_enh-04] | Moderator (OPPO) |
| 8.3.4 | Other | |
| R1-2007659 | Discussion on propagation delay compensation enhancements | vivo |
| R1-2007711 | Propagation Delay Compensation Enhancements for Time Synchronization | Ericsson |
| R1-2007853 | Discussion on propagation delay compensation enhancements | CATT |
| R1-2008061 | Discussion on propagation delay compensation enhancements | LG Electronics |
| R1-2008163 | Discussion for propagation delay compensation enhancements | Samsung |
| R1-2008283 | Enhancements for Propagation Delay Compensation | OPPO |
| R1-2008318 | Enhancements for support of time synchronization | Huawei, HiSilicon |
| R1-2008464 | Discussion on Orphan symbol handling for unlicensed spectrum | Apple |
| R1-2008825 | Discussion on propagation delay compensation enhancements | ZTE |
| R1-2008844 | Discussion on enhancements for propagation delay compensation | Nokia, Nokia Shanghai Bell |
| R1-2008988 | On propagation delay compensation for enhanced timing synchronization | Intel Corporation |
| R1-2009014 | Processing time for COT sharing in FBE | ETRI |
| R1-2009261 | Enhancements for support of time synchronization for enhanced IIoT and URLLC | Qualcomm Incorporated |
| R1-2009551 | Feature lead summary on propagation delay compensation enhancements (AI 8.3.4) | Moderator (Huawei) |
| 8.4 | Solutions for NR to support non-terrestrial networks (NTN) | |
| R1-2009051 | NR_NTN_solutions work plan | THALES |
| R1-2009061 | Support of smart phones in NTN | Thales, ESA, Firstnet, Fraunhofer IIS, Fraunhofer HHI, Qualcomm, Reliance Jio, Intelsat, Hughes Network Systems |
| R1-2009834 | Session notes for 8.4 (Solutions for NR to support non-terrestrial networks (NTN)) | Ad-Hoc Chair (Ericsson) |
| 8.4.1 | Timing relationship enhancements | |
| R1-2007569 | Discussion on timing relationship enhancements for NTN | Huawei, HiSilicon |
| R1-2007660 | Discussion on timing relationship enhancements for NR-NTN | vivo |
| R1-2007854 | Timing relationship discussion for NTN | CATT |
| R1-2007991 | Discussion on timing relationship enhancements for NR NTN | China Telecom |
| R1-2008010 | Discussion on timing relationship enhancements for NTN | CMCC |
| R1-2008164 | Timing relationship enhancements for NTN | Samsung |
| R1-2008253 | Discusson on timing relationship enhancement | OPPO |
| R1-2008359 | Calculation of timing relationship offsets | Sony |
| R1-2008410 | Discussions on timing relationship enhancements in NTN | LG Electronics |
| R1-2008465 | Timing Relationship Enhancement in NTN | Apple |
| R1-2008722 | Discussion on timing relationship enhancements for NTN | Fraunhofer IIS, Fraunhofer HHI |
| R1-2008808 | Timing relationship enhancements for NR-NTN | MediaTek Inc., Eutelsat |
| R1-2008850 | Discussion on timing relationship for NTN | ZTE |
| R1-2008922 | Discussion on NTN timing relationship | Lenovo, Motorola Mobility |
| R1-2008989 | On timing relationship enhancements for NTN | Intel Corporation |
| R1-2009015 | Discussion on timing relationship enhancement for NTN | ETRI |
| R1-2009032 | Discussion on the timing relationship enhancement for NTN | Xiaomi |
| R1-2009049 | Timing relationship enhancement for NTN | Panasonic Corporation |
| R1-2009057 | Timing relationship enhancements in NTN | Asia Pacific Telecom co. Ltd |
| R1-2009076 | Timing relationship enhancements to support NTN | CAICT |
| R1-2009091 | On timing relationship enhancements for NTN | Ericsson |
| R1-2009116 | On timing relationship for NTN | InterDigital, Inc. |
| R1-2009152 | Consideration on timing relationship enhancements | Spreadtrum Communications |
| R1-2009186 | Discussion on timing relationship enhancements for NTN | NTT DOCOMO, INC. |
| R1-2009242 | Views on DL-UL timing relationship for NTN operation | Nokia, Nokia Shanghai Bell |
| R1-2009262 | Enhancements on Timing Relationship for NTN | Qualcomm Incorporated |
| R1-2009373 | Feature lead summary#1 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2009498 | Feature lead summary#2 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2009603 | Feature lead summary#3 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2009733 | Feature lead summary#4 on timing relationship enhancements | Moderator (Ericsson) |
| 8.4.2 | Enhancements on UL time and frequency synchronization | |
| R1-2007570 | Discussion on UL time and frequency synchronization enhancement for NTN | Huawei, HiSilicon |
| R1-2007661 | Discussion on UL time and frequency synchronization enhancements for NR-NTN | vivo |
| R1-2007855 | UL time and frequency compensation for NTN | CATT |
| R1-2008011 | Enhancements on uplink timing advance for NTN | CMCC |
| R1-2008165 | Enhancements on UL time and frequency synchronization for NTN | Samsung |
| R1-2008254 | Discussion on UL time and frequency synchronization | OPPO |
| R1-2008360 | Enhancement for UL time synchronization | Sony |
| R1-2008411 | Discussions on UL time and frequency synchronization enhancements in NTN | LG Electronics |
| R1-2008466 | Uplink Time and Frequency Synchronization for NTN | Apple |
| R1-2008809 | UL Time and Frequency Synchronisation for NR-NTN | MediaTek Inc., Eutelsat |
| R1-2008851 | Discussion on UL synchronization for NTN | ZTE |
| R1-2008867 | Satellite Position Accuracy | Eutelsat S.A. |
| R1-2008923 | Discussion on NTN TA indication | Lenovo, Motorola Mobility |
| R1-2008990 | On UL time and frequency synchronization for NTN | Intel Corporation |
| R1-2009016 | Discussion on UL timing synchronization for NTN | ETRI |
| R1-2009033 | Discussion on UL time and frequency synchronization for NTN | Xiaomi |
| R1-2009058 | UL time and frequency synchronization in NTN | Asia Pacific Telecom co. Ltd |
| R1-2009068 | Satellite Position Accuracy | Eutelsat S.A. |
| R1-2009075 | Discussion on UL time synchronization acquisition | Mitsubishi Electric RCE |
| R1-2009077 | Considerations on Enhancements on UL Time Synchronization in NTN | CAICT |
| R1-2009092 | On UL time and frequency synchronization enhancements for NTN | Ericsson |
| R1-2009097 | NTN UL time frequency | PANASONIC R&D Center Germany |
| R1-2009117 | On UL time/frequency synchronization for NTN | InterDigital, Inc. |
| R1-2009153 | Consideration on enhancements on UL time and frequency synchronization | Spreadtrum Communications |
| R1-2009243 | Discussion on time and frequency synchronization for NTN systems | Nokia, Nokia Shanghai Bell |
| R1-2009263 | UL time and frequency synchronization for NTN | Qualcomm Incorporated |
| R1-2009292 | UL time synchronization for NTN systems | CEWiT |
| R1-2009298 | Considerations on UL timing and frequency synchronization | THALES |
| R1-2009485 | Feature lead summary on enhancements on UL timing and frequency synchronization | Moderator (Thales) |
| R1-2009556 | Feature lead summary#2 on enhancements on UL timing and frequency synchronization | Moderator (Thales) |
| R1-2009672 | Feature lead summary#3 on enhancements on UL timing and frequency synchronization | Moderator (Thales) |
| R1-2009697 | Feature lead summary#4 on enhancements on UL timing and frequency synchronization | Moderator (Thales) |
| R1-2009748 | Feature lead summary#5 on enhancements on UL timing and frequency synchronization | Moderator (Thales) |
| 8.4.3 | Enhancements on HARQ | |
| R1-2007571 | Discussion on HARQ enhancement for NTN | Huawei, HiSilicon |
| R1-2007662 | Discussion on HARQ enhancements for NR-NTN | vivo |
| R1-2007856 | HARQ operation enhancement for NTN | CATT |
| R1-2008012 | Enhancements on HARQ for NTN | CMCC |
| R1-2008166 | Enhancements on HARQ for NTN | Samsung |
| R1-2008255 | Discussion on HARQ enhancement | OPPO |
| R1-2008256 | Discussion on other aspects | OPPO |
| R1-2008361 | Enhancements on HARQ for NTN | Sony |
| R1-2008412 | Discussions on HARQ enhancements in NTN | LG Electronics |
| R1-2008467 | HARQ Enhancements for NTN | Apple |
| R1-2008802 | INTELLIGENT PACKET REPETITION IN MOBILE SATELLITE SERVICE (MSS) LINKS TO OVERCOME CHANNEL BLOCKAGES | Ligado Networks |
| R1-2008810 | HARQ in NR-NTN | MediaTek Inc. |
| R1-2008852 | Discussion on HARQ for NTN | ZTE |
| R1-2008881 | Discussion on HARQ for NTN | Nomor Research GmbH, Thales |
| R1-2008924 | Enhancements on HARQ for NTN | Lenovo, Motorola Mobility |
| R1-2008991 | On HARQ enhancements for NTN | Intel Corporation |
| R1-2009017 | Discussion on HARQ Enhancements for NTN | ETRI |
| R1-2009034 | Discussion on the HARQ enhancement for NTN | Xiaomi |
| R1-2009050 | HARQ enhancement for NTN | Panasonic Corporation |
| R1-2009059 | Enhancements on HARQ in NTN | Asia Pacific Telecom co. Ltd |
| R1-2009078 | HARQ enhancements to support NTN | CAICT |
| R1-2009093 | On HARQ enhancements for NTN | Ericsson |
| R1-2009118 | On HARQ enhancement for NTN | InterDigital, Inc. |
| R1-2009154 | Consideration on enhancements on HARQ | Spreadtrum Communications |
| R1-2009244 | Further discussion on HARQ operation for NTN systems | Nokia, Nokia Shanghai Bell |
| R1-2009264 | Enhancements on HARQ for NTN | Qualcomm Incorporated |
| R1-2009420 | Summary of AI 8.4.3 for HARQ in NTN | Moderator (ZTE) |
| R1-2009657 | Summary#2 of AI 8.4.3 for HARQ in NTN | Moderator (ZTE) |
| R1-2009695 | Summary#3 of AI 8.4.3 for HARQ in NTN | Moderator (ZTE) |
| 8.4.4 | Other | |
| R1-2007663 | Discussion on other aspects for NR-NTN | vivo |
| R1-2007857 | Other Aspects of NR-NTN | CATT |
| R1-2008013 | Other Aspects for NTN | CMCC |
| R1-2008167 | Remaining issues for NTN | Samsung |
| R1-2008319 | Discussion on other design aspects for NTN | Huawei, HiSilicon |
| R1-2008362 | Discussion on beam management and polarization for NTN | Sony |
| R1-2008413 | Discussions on other aspects of NTN | LG Electronics |
| R1-2008468 | Other Aspects of NR NTN | Apple |
| R1-2008803 | Discussion on the applicability of DFT-S-OFDM for NTN | CAICT |
| R1-2008804 | Discussion on the applicability of DFT-S-OFDM for NTN | CAICT |
| R1-2008807 | Considerations on Earth-fixed Beams and Earth-moving beams | CAICT |
| R1-2008811 | Other Aspects of NR-NTN | MediaTek Inc. |
| R1-2008812 | Summary #1 of 8.4.4 Other Aspects of NR-NTN | MediaTek Inc. |
| R1-2008853 | Discussion on additional enhancement for NTN | ZTE |
| R1-2008885 | Study Cases and Parameters for System-Level Simulations in NTN WI | Nomor Research GmbH, Thales |
| R1-2008925 | Discussion on NTN beam management | Lenovo, Motorola Mobility |
| R1-2009026 | SSB, beam management and polarization signaling for NTN | Panasonic |
| R1-2009035 | Discussion on the beam management for NTN | Xiaomi |
| R1-2009094 | On other enhancements for NTN | Ericsson |
| R1-2009119 | On feeder link switch and beam management for NTN | InterDigital, Inc. |
| R1-2009237 | Discussion on the applicability of DFT-S-OFDM for NTN | CAICT |
| R1-2009245 | Additional aspects for NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2009249 | Discussion on beam management of NTN | CAICT |
| R1-2009265 | BWP operation and other issues for NTN | Qualcomm Incorporated |
| R1-2009487 | Summary #2 of 8.4.4 Other Aspects of NR-NTN | MediaTek Inc. |
| R1-2009581 | Summary #3 of 8.4.4 Other Aspects of NR-NTN | MediaTek Inc. |
| R1-2009736 | Summary #4 of 8.4.4 Other Aspects of NR-NTN | MediaTek Inc. |
| 8.5 | Study on NR Positioning Enhancements | |
| R1-2008762 | TR 38.857 v0.1.0: Study on NR Positioning Enhancements | Rapporteur (Ericsson) |
| R1-2009400 | TR 38.857 v0.1.0: Study on NR Positioning Enhancements | Rapporteur (Ericsson) |
| R1-2009418 | TR 38.857 v0.1.0: Study on NR Positioning Enhancements | Rapporteur (Ericsson) |
| R1-2009430 | TR 38.857 v0.1.0: Study on NR Positioning Enhancements | Rapporteur (Ericsson) |
| R1-2009431 | TR 38.857 v0.1.1: Study on NR Positioning Enhancements | Rapporteur (Ericsson) |
| R1-2009544 | TR 38.857 v0.1.1: Study on NR Positioning Enhancements | Rapporteur (Ericsson) |
| R1-2009545 | TR 38.857 v0.1.2: Study on NR Positioning Enhancements | Rapporteur (Ericsson) |
| R1-2009665 | TR 38.857 v0.1.2: Study on NR Positioning Enhancements | Rapporteur (Ericsson) |
| R1-2009670 | TR 38.857 v0.2.0: Study on NR Positioning Enhancements | Rapporteur (Ericsson) |
| R1-2009671 | TR 38.857 v0.2.1: Study on NR Positioning Enhancements | Rapporteur (Ericsson) |
| R1-2009743 | TR 38.857 v0.2.2: Study on NR Positioning Enhancements | Rapporteur (Ericsson) |
| R1-2009745 | TR 38.857 v0.3.0: Study on NR Positioning Enhancements | Rapporteur (Ericsson) |
| R1-2009835 | Session notes for 8.5 (Study on NR Positioning Enhancements) | Ad-Hoc Chair (Ericsson) |
| R1-2009842 | TR 38.857 v0.4.0: Study on NR Positioning Enhancements | Rapporteur (Ericsson) |
| 8.5.1 | Additional scenarios for evaluation | |
| R1-2007575 | Scenarios and evaluation assumption for IIoT positioning | Huawei, HiSilicon |
| R1-2007664 | Discussion on additional scenarios for NR positioning evaluation | vivo |
| R1-2007753 | Remaining issues on evaluation assumptions | ZTE |
| R1-2007858 | Remaining issues on additional scenarios for evaluation of NR Positioning Enhancements | CATT |
| R1-2007907 | Remaining Issues on Evaluation Assumptions | FUTUREWEI |
| R1-2007944 | NR positioning scenarios | Intel Corporation |
| R1-2008014 | Remaining issues on target performance requirement of IIoT use case | CMCC |
| R1-2008224 | Discussion on Additional Scenarios for Evaluation of NR Positioning | OPPO |
| R1-2008299 | Additional scenarios for evaluation of NR positioning | Nokia, Nokia Shanghai Bell |
| R1-2008363 | Considerations on Additional Scenarios for Evaluation | Sony |
| R1-2008415 | Discussions on additional scenarios for evaluation for NR positioning | LG Electronics |
| R1-2008488 | Discussion on evaluation assumptions for latency | InterDigital, Inc. |
| R1-2008617 | Considerations on Additional Scenarios for Evaluation | Qualcomm Incorporated |
| R1-2008763 | Remaining details on additional scenarios for evaluation | Ericsson |
| R1-2009343 | FL summary for additional scenarios for evaluation | Moderator (Ericsson) |
| R1-2009364 | Output#1 of [103-e-NR-ePos-01] Email discussion on additional scenarios for evaluation | Moderator (Ericsson) |
| R1-2009417 | Output#2 of [103-e-NR-ePos-01] Email discussion on additional scenarios for evaluation | Moderator (Ericsson) |
| R1-2009503 | Output#3 of [103-e-NR-ePos-01] Email discussion on additional scenarios for evaluation | Moderator (Ericsson) |
| 8.5.2 | Evaluation of achievable positioning accuracy and latency | |
| R1-2007576 | Evaluation results for Rel-16 positioning and Rel-17 enhancement | Huawei, HiSilicon |
| R1-2007665 | Evaluation of NR positioning performance | vivo |
| R1-2007720 | Evaluation of achievable positioning accuracy | BUPT |
| R1-2007754 | Evaluation of achievable accuracy and latency | ZTE |
| R1-2007859 | Discussion of evaluation of NR positioning performance | CATT |
| R1-2007908 | NLOS Identification and Mitigation | FUTUREWEI |
| R1-2007945 | NR positioning evaluation | Intel Corporation |
| R1-2007997 | NR Positioning Latency Evaluations | Lenovo, Motorola Mobility |
| R1-2008225 | Evaluation of NR positioning in IIOT scenario | OPPO |
| R1-2008300 | Results on evaluation of achievable positioning accuracy and latency | Nokia, Nokia Shanghai Bell |
| R1-2008364 | Discussion on Performance evaluation of Rel-17 positioning | Sony |
| R1-2008416 | Discussions on evaluation of achievable positioning accuracy and latency for NR positioning | LG Electronics |
| R1-2008489 | Evaluation of achievable positioning latency | InterDigital, Inc. |
| R1-2008618 | Evaluation of achievable Positioning Accuracy & Latency | Qualcomm Incorporated |
| R1-2008709 | Evaluation of positioning enhancements | Fraunhofer IIS, Fraunhofer HHI |
| R1-2008720 | Positioning evaluation results on potential enhancements for additional use cases | CEWiT |
| R1-2008764 | Evaluation of achievable positioning accuracy and latency | Ericsson |
| R1-2009345 | Feature lead summary for evaluation of NR Positioning enhancements | Moderator (Intel) |
| R1-2009361 | Evaluation of achievable Positioning Accuracy & Latency | Qualcomm Incorporated |
| R1-2009375 | Summary #1 of RAN WG1 E-mail Discussion [103-e-NR-ePos-02] - AI 8.5.2 | Moderator (Intel Corporation) |
| R1-2009376 | Summary #2 of RAN WG1 E-mail Discussion [103-e-NR-ePos-02] - AI 8.5.2 | Moderator (Intel Corporation) |
| R1-2009390 | Update of Evaluation Results for NR Positioning | Intel Corporation |
| R1-2009406 | Summary #3 of RAN WG1 E-mail Discussion [103-e-NR-ePos-02] - AI 8.5.2 | Moderator (Intel Corporation) |
| R1-2009407 | Summary #4 of RAN WG1 E-mail Discussion [103-e-NR-ePos-02] - AI 8.5.2 | Moderator (Intel Corporation) |
| R1-2009428 | Evaluation of positioning enhancements | Fraunhofer IIS, Fraunhofer HHI |
| R1-2009433 | Evaluation results for Rel-16 positioning and Rel-17 enhancement | Huawei, HiSilicon |
| R1-2009502 | Discussion on Performance evaluation of Rel-17 positioning | Sony |
| R1-2009555 | Results on evaluation of achievable positioning accuracy and latency | Nokia, Nokia Shanghai Bell |
| R1-2009606 | Summary #5 of RAN WG1 E-mail Discussion [103-e-NR-ePos-02] - AI 8.5.2 | Moderator (Intel Corporation) |
| R1-2009607 | Summary #6 of RAN WG1 E-mail Discussion [103-e-NR-ePos-02] - AI 8.5.2 | Moderator (Intel Corporation) |
| R1-2009708 | Evaluation of achievable Positioning Accuracy & Latency | Qualcomm Incorporated |
| R1-2009762 | Discussion on DL PRS and SRS for Positioning Measurement Time ([103-e-NR-ePos-02]) | Moderator (Intel Corporation) |
| 8.5.3 | Potential positioning enhancements | |
| R1-2007552 | Positioning Enhancements | FUTUREWEI |
| R1-2007577 | Positioning enhancement in Rel-17 | Huawei, HiSilicon |
| R1-2007666 | Discussion on potential positioning enhancements | vivo |
| R1-2007721 | Potential positioning enhancements | BUPT |
| R1-2007755 | Discussion on potential NR positioning enhancements | ZTE |
| R1-2007860 | Discussion of NR positioning enhancements | CATT |
| R1-2007886 | Potential positioning enhancements | TCL Communication Ltd. |
| R1-2007946 | NR positioning enhancements | Intel Corporation |
| R1-2007998 | Potential NR Positioning Enhancements | Lenovo, Motorola Mobility |
| R1-2008015 | Discussion on potential positioning enhancements | CMCC |
| R1-2008083 | Potential positioning enhancements | Xiaomi |
| R1-2008168 | Potential positioning enhancements | Samsung |
| R1-2008226 | Discussions on NR Positioning Enhancements | OPPO |
| R1-2008301 | Views on potential positioning enhancements | Nokia, Nokia Shanghai Bell |
| R1-2008365 | Considerations on potential positioning enhancements | Sony |
| R1-2008417 | Discussions on potential enhancements for NR positioning | LG Electronics |
| R1-2008491 | Discussion on potential positioning enhancements | InterDigital, Inc. |
| R1-2008519 | Views on positioning enhancement for Rel-17 | MediaTek Inc. |
| R1-2008550 | Discussion on potential techniques for NR Positioning Enhancements | NTT DOCOMO, INC. |
| R1-2008619 | Potential Positioning Enhancements for NR Rel-17 Positioning | Qualcomm Incorporated |
| R1-2008710 | Potential positioning enhancements | Fraunhofer IIS |
| R1-2008718 | Discussion on positioning enhancements for Release 17 | CEWiT |
| R1-2008765 | Potential positioning enhancements | Ericsson |
| R1-2008841 | Potential positioning enhancements | Fraunhofer IIS, Fraunhofer HHI |
| R1-2009285 | Discussion on Potential positioning enhancements | CAICT |
| R1-2009314 | FL Summary for Potential Positioning Enhancements | Moderator (CATT) |
| R1-2009366 | FL Summary#2 for Potential Positioning Enhancements | Moderator (CATT) |
| R1-2009395 | FL Summary#3 for Potential Positioning Enhancements | Moderator (CATT) |
| R1-2009396 | FL Summary#4 for Potential Positioning Enhancements | Moderator (CATT) |
| R1-2009397 | FL Summary#5 for Potential Positioning Enhancements | Moderator (CATT) |
| R1-2009398 | FL Summary#6 for Potential Positioning Enhancements | Moderator (CATT) |
| R1-2009399 | FL Summary#7 for Potential Positioning Enhancements | Moderator (CATT) |
| R1-2009673 | FL Summary#8 for Potential Positioning Enhancements | Moderator (CATT) |
| R1-2009678 | FL Summary#9 for Potential Positioning Enhancements | Moderator (CATT) |
| R1-2009679 | FL Summary#10 for Potential Positioning Enhancements | Moderator (CATT) |
| 8.5.4 | Other | |
| R1-2007667 | Discussion on new techniques for NR positioning | vivo |
| R1-2007756 | Channel state estimation based on prior channel information | ZTE |
| R1-2007861 | Discussion of NLOS channel modelling and network time synchronization for NR positioning | CATT |
| R1-2007910 | Polarization-based LOS Detection | FUTUREWEI |
| R1-2008169 | Uplink Transmission Based Relative Positioning | Samsung |
| R1-2008227 | Analysis of NR Positioning Requirements | OPPO |
| R1-2008302 | Additional considerations for positioning enhancements | Nokia, Nokia Shanghai Bell |
| R1-2008321 | Evaluations on additional channel model features | Huawei, HiSilicon |
| R1-2008492 | Discussion on positioning failure and mobility modeling | InterDigital, Inc. |
| R1-2008766 | PRS with cyclic shifts | Ericsson |
| 8.6 | Study on Support of Reduced Capability NR Devices | |
| R1-2007528 | TR38.875 skeleton updates for Study on support of reduced capability NR devices | Rapporteur (Ericsson) |
| R1-2009293 | FL summary on RedCap evaluation results | Moderator (Ericsson, Apple, Qualcomm) |
| R1-2009490 | TR38.875 v0.0.3 Study on support of reduced capability NR devices | Rapporteur (Ericsson) |
| R1-2009816 | TR38.875 v0.1.0 Study on support of reduced capability NR devices | Rapporteur (Ericsson) |
| R1-2009843 | FL summary #1 for TR38.875 update for RedCap | Moderator (Ericsson) |
| R1-2009844 | FL summary #2 for TR38.875 update for RedCap | Moderator (Ericsson) |
| R1-2009850 | TR38.875 v0.1.0 Study on support of reduced capability NR devices | Rapporteur (Ericsson) |
| 8.6.1 | Potential UE complexity reduction features | |
| R1-2007529 | Potential UE complexity reduction features for RedCap | Ericsson |
| R1-2007534 | Complexity reduction features for RedCap UEs | FUTUREWEI |
| R1-2007596 | Potential UE complexity reduction features | Huawei, HiSilicon |
| R1-2007668 | Complexity reduction for Reduced Capability NR devices | vivo, Guangdong Genius |
| R1-2007715 | Potential UE complexity reduction features | ZTE |
| R1-2007862 | Discussion on UE complexity reduction features | CATT |
| R1-2007887 | Potential UE complexity reduction features | TCL Communication Ltd. |
| R1-2007947 | On potential UE complexity reduction features for RedCap | Intel Corporation |
| R1-2008016 | Discussion on UE complexity reduction features | CMCC |
| R1-2008048 | Discussion on potential UE complexity reduction features | LG Electronics |
| R1-2008068 | UE complexity reduction features | Nokia, Nokia Shanghai Bell |
| R1-2008084 | Discussion on the complexity reduction for reduced capability device | Xiaomi |
| R1-2008100 | Discussion on potential UE complexity reduction features | Spreadtrum Communications |
| R1-2008114 | Discussion on bandwidth related features for RedCap devices | NEC |
| R1-2008170 | UE complexity reduction | Samsung |
| R1-2008260 | Discussion on UE complexity reduction | OPPO |
| R1-2008294 | UE complexity reduction features for RedCap | Lenovo, Motorola Mobility |
| R1-2008315 | Reduced Capability UE Complexity Reduction Features | Sierra Wireless, S.A. |
| R1-2008366 | On potential complexity reduction techniques for NR devices | Sony |
| R1-2008382 | Discussion on potential UE complexity reduction features | Panasonic Corporation |
| R1-2008394 | Discussion on Potential UE complexity reduction features | Sharp |
| R1-2008469 | Potential UE complexity reduction features for RedCap | Apple |
| R1-2008510 | On complexity reduction features for NR RedCap UEs | MediaTek Inc. |
| R1-2008551 | Discussion on potential UE complexity reduction features for RedCap | NTT DOCOMO, INC. |
| R1-2008581 | Discussion on potential UE complexity reduction features | ASUSTeK |
| R1-2008620 | Complexity Reduction for RedCap Devices | Qualcomm Incorporated |
| R1-2008684 | UE complexity reduction features for reduced capability NR devices | InterDigital, Inc. |
| R1-2008738 | Complexity reduction features for RedCap UE | Sequans Communications |
| R1-2008837 | Potential UE complexity reduction features for RedCap | Ericsson |
| R1-2008857 | Discussion on the complexity reduction for reduced capability device | Beijing Xiaomi Software Tech |
| R1-2008869 | FL summary #1 for Potential UE complexity reduction features for RedCap | Moderator (Ericsson) |
| R1-2008875 | UE complexity reduction | Samsung |
| R1-2009025 | On potential UE complexity reduction features for RedCap | Intel Corporation |
| R1-2009212 | Complexity reduction for Reduced Capability NR devices | vivo, Guangdong Genius |
| R1-2009318 | Potential UE complexity reduction features | Huawei, HiSilicon |
| R1-2009391 | FL summary #2 for Potential UE complexity reduction features for RedCap | Moderator (Ericsson) |
| R1-2009393 | FL summary #3 for Potential UE complexity reduction features for RedCap | Moderator (Ericsson) |
| R1-2009394 | FL summary #4 for Potential UE complexity reduction features for RedCap | Moderator (Ericsson) |
| R1-2009543 | On complexity reduction features for NR RedCap UEs | MediaTek Inc. |
| R1-2009651 | FL summary #5 for Potential UE complexity reduction features for RedCap | Moderator (Ericsson) |
| R1-2009652 | FL summary #6 for Potential UE complexity reduction features for RedCap | Moderator (Ericsson) |
| R1-2009795 | FL summary #7 for Potential UE complexity reduction features for RedCap | Moderator (Ericsson) |
| R1-2009803 | FL summary #8 for Potential UE complexity reduction features for RedCap | Moderator (Ericsson) |
| 8.6.2 | Reduced PDCCH monitoring | |
| R1-2007530 | Reduced PDCCH monitoring for RedCap | Ericsson |
| R1-2007535 | Power savings for RedCap UEs | FUTUREWEI |
| R1-2007597 | Power saving for reduced capability devices | Huawei, HiSilicon |
| R1-2007625 | Discussion on PDCCH monitoring reduction for RedCap UEs | Panasonic |
| R1-2007669 | Reduced PDCCH monitoring for Reduced Capability NR devices | vivo, Guangdong Genius |
| R1-2007716 | Consideration on reduced PDCCH monitoring | ZTE |
| R1-2007863 | Discussion on PDCCH monitoring reduction | CATT |
| R1-2007888 | Reduced PDCCH monitoring | TCL Communication Ltd. |
| R1-2007948 | On reduced PDCCH monitoring for RedCap UEs | Intel Corporation |
| R1-2008017 | Discussion on PDCCH monitoring reduction | CMCC |
| R1-2008049 | Discussion on PDCCH monitoring for reduced capability NR devices | LG Electronics |
| R1-2008069 | Reduced PDCCH monitoring | Nokia, Nokia Shanghai Bell |
| R1-2008085 | Discussion on reduced PDCCH monitoring for reduced capability device | Xiaomi |
| R1-2008105 | Discussion on reduced PDCCH monitoring | Spreadtrum Communications |
| R1-2008115 | Reduced PDCCH monitoring for REDCAP NR devices | NEC |
| R1-2008171 | Reduced PDCCH monitoring | Samsung |
| R1-2008261 | Solutions of reduced PDCCH monitoring | OPPO |
| R1-2008336 | PDCCH monitoring at reduced capability UE | Lenovo, Motorola Mobility |
| R1-2008395 | Reduced PDCCH Monitoring for RedCap Devices | Sharp |
| R1-2008470 | Reduced PDCCH Monitoring for RedCap Devices | Apple |
| R1-2008471 | Feature lead summary #1 on reduced PDCCH monitoring | Moderator (Apple) |
| R1-2008511 | Discussion on reduced PDCCH monitoring for NR RedCap UEs | MediaTek Inc. |
| R1-2008552 | Discussion on reduced PDCCH monitoring for RedCap | NTT DOCOMO, INC. |
| R1-2008621 | PDCCH Monitoring Reduction and Power Saving for RedCap Devices | Qualcomm Incorporated |
| R1-2008685 | Reduced PDCCH monitoring for reduced capability NR devices | InterDigital, Inc. |
| R1-2008712 | Reduced PDCCH Monitoring for RedCap UEs | Fraunhofer HHI, Fraunhofer IIS |
| R1-2008727 | Discussion on PDCCH monitoring for RedCap UE | WILUS Inc. |
| R1-2008739 | Reduced PDCCH monitoring for RedCap UE | Sequans Communications |
| R1-2008894 | Solutions of reduced PDCCH monitoring | OPPO |
| R1-2009370 | Feature lead summary #2 on reduced PDCCH monitoring | Moderator (Apple) |
| R1-2009411 | Feature lead summary #3 on reduced PDCCH monitoring | Moderator (Apple) |
| R1-2009493 | Feature lead summary #4 on reduced PDCCH monitoring | Moderator (Apple) |
| R1-2009571 | Feature lead summary #5 on reduced PDCCH monitoring | Moderator (Apple) |
| R1-2009659 | Feature lead summary #6 on reduced PDCCH monitoring | Moderator (Apple) |
| R1-2009720 | Feature lead summary #7 on reduced PDCCH monitoring | Moderator (Apple) |
| R1-2009766 | Feature lead summary #8 on reduced PDCCH monitoring | Moderator (Apple) |
| R1-2009783 | Feature lead summary #9 on reduced PDCCH monitoring | Moderator (Apple) |
| R1-2009813 | Feature lead summary #10 on reduced PDCCH monitoring | Moderator (Apple) |
| R1-2009839 | Feature lead summary #11 on reduced PDCCH monitoring | Moderator (Apple) |
| 8.6.3 | Coverage recovery and capacity impact | |
| R1-2007531 | Coverage recovery and capacity impact for RedCap | Ericsson |
| R1-2007536 | Coverage recovery for RedCap | FUTUREWEI |
| R1-2007598 | Functionality for coverage recovery | Huawei, HiSilicon |
| R1-2007670 | Discussion on coverage recovery, capacity and spectrum efficiency impact | vivo, Guangdong Genius |
| R1-2007717 | Discussion on coverage recovery for RedCap UE | ZTE |
| R1-2007864 | Coverage recovery for reduced capability NR devices | CATT |
| R1-2007889 | Coverage recovery and capacity impact | TCL Communication Ltd. |
| R1-2007949 | On coverage recovery for RedCap UEs | Intel Corporation |
| R1-2007990 | Coverage Recovery and Capacity Impact | Panasonic Corporation |
| R1-2008018 | Discussion on coverage recovery for RedCap UEs | CMCC |
| R1-2008050 | Discussion on the coverage recovery of reduced capability NR devices | LG Electronics |
| R1-2008070 | Functionality for coverage recovery | Nokia, Nokia Shanghai Bell |
| R1-2008086 | Discussion on coverage recovery for reduced capability device | Xiaomi |
| R1-2008102 | Discussion on coverage recovery and capacity impact | Spreadtrum Communications |
| R1-2008172 | Coverage recovery for low capability device | Samsung |
| R1-2008262 | Discussion on coverage recovery issues and evaluation | OPPO |
| R1-2008295 | Coverage recovery for RedCap | Lenovo, Motorola Mobility |
| R1-2008367 | Coverage recovery for Redcap devices | Sony |
| R1-2008396 | Coverage recovery for reduced capability UEs | Sharp |
| R1-2008472 | Functionality for Coverage Recovery for RedCap | Apple |
| R1-2008512 | Discussion on coverage recovery for NR RedCap UEs | MediaTek Inc. |
| R1-2008518 | On coverage recovery for reduced capability UEs | Convida Wireless |
| R1-2008553 | Discussion on coverage recovery for RedCap | NTT DOCOMO, INC. |
| R1-2008622 | Coverage Recovery for RedCap Devices | Qualcomm Incorporated |
| R1-2008686 | Coverage recovery for reduced capability NR devices | InterDigital, Inc. |
| R1-2008728 | Discussion on Coverage Recovery for RedCap UE | WILUS Inc. |
| R1-2008740 | Coverage recovery for RedCap UE | Sequans Communications |
| R1-2008813 | Functionality for coverage recovery | Huawei |
| R1-2008865 | Coverage recovery and capacity impact for RedCap | Ericsson |
| R1-2008876 | Considerations for coverage recovery | ITL |
| R1-2009173 | Coverage recovery for RedCap | Lenovo, Motorola Mobility |
| R1-2009217 | Coverage Recovery and Capacity Impact | Panasonic Corporation |
| R1-2009310 | Coverage Recovery for RedCap Devices | Qualcomm Incorporated |
| R1-2009311 | FL summary #1 on coverage recovery and capacity impact for RedCap UEs | Moderator (Qualcomm) |
| R1-2009365 | FL summary #2 on coverage recovery and capacity impact for RedCap UEs | Moderator (Qualcomm) |
| R1-2009479 | FL summary #3 on coverage recovery and capacity impact for RedCap UEs | Moderator (Qualcomm) |
| R1-2009580 | FL summary #4 on coverage recovery and capacity impact for RedCap UEs | Moderator (Qualcomm) |
| R1-2009616 | Discussion on coverage recovery, capacity and spectrum efficiency impact | vivo, Guangdong Genius |
| R1-2009660 | FL summary #5 on coverage recovery and capacity impact for RedCap UEs | Moderator (Qualcomm) |
| R1-2009721 | FL summary #6 on coverage recovery and capacity impact for RedCap UEs | Moderator (Qualcomm) |
| R1-2009722 | FL summary #7 on coverage recovery and capacity impact for RedCap UEs | Moderator (Qualcomm) |
| R1-2009782 | Functionality for coverage recovery | Huawei |
| R1-2009796 | FL summary #8 on coverage recovery and capacity impact for RedCap UEs | Moderator (Qualcomm) |
| R1-2009817 | FL summary #9 (post e-meeting) on coverage recovery and capacity impact for RedCap UEs | Moderator (Qualcomm) |
| 8.6.4 | Framework and Principles for Reduced Capability | |
| R1-2007532 | Framework and principles for RedCap | Ericsson |
| R1-2007537 | Framework for RedCap UEs | FUTUREWEI |
| R1-2007599 | Framework and principles for reduced capability devices | Huawei, HiSilicon |
| R1-2007671 | Framework and Principles for Reduced Capability | vivo, Guangdong Genius |
| R1-2007718 | Views on Framework and Principles for Reduced Capability | ZTE |
| R1-2007865 | Framework and principles for reduced capability NR devices | CATT |
| R1-2007950 | Framework and principles for introduction of RedCap UEs | Intel Corporation |
| R1-2008019 | Discussion on design principles and definition for RedCap device type | CMCC |
| R1-2008051 | Consideration on the framework to support reduced capability NR devices | LG Electronics |
| R1-2008071 | Framework and Principles for Reduced Capability UE | Nokia, Nokia Shanghai Bell |
| R1-2008087 | Framework and Principles for Reduced Capability | Xiaomi |
| R1-2008101 | Discussion on Framework and Principles for Reduced Capability | Spreadtrum Communications |
| R1-2008173 | Framework and Principles for Reduced Capability | Samsung |
| R1-2008263 | Further considerations on reduced UE capability | OPPO |
| R1-2008290 | Discussion on Framework and Principles for Reduced Capability | Panasonic |
| R1-2008296 | Framework and Principles for RedCap | Lenovo, Motorola Mobility |
| R1-2008473 | Framework and principles for RedCap | Apple |
| R1-2008513 | On the framework for RedCap UEs | MediaTek Inc. |
| R1-2008554 | Discussion on framework and principles for RedCap | NTT DOCOMO, INC. |
| R1-2008555 | Summary on Framework and Principles for Reduced Capability | Moderator (NTT DOCOMO, INC.) |
| R1-2008623 | Standardization Framework and Design Principles for RedCap Devices | Qualcomm Incorporated |
| R1-2008687 | Framework and Principles for Reduced Capability | InterDigital, Inc. |
| R1-2008741 | Framework and principles for RedCap UE | Sequans Communications |
| R1-2009381 | Summary#2 on Framework and Principles for Reduced Capability | Moderator (NTT DOCOMO, INC.) |
| R1-2009534 | Summary#3 on Framework and Principles for Reduced Capability | Moderator (NTT DOCOMO, INC.) |
| R1-2009732 | Summary#4 on Framework and Principles for Reduced Capability | Moderator (NTT DOCOMO, INC.) |
| 8.6.5 | Other | |
| R1-2007533 | UE identification and access restriction for RedCap | Ericsson |
| R1-2007538 | Identification for RedCap UEs | FUTUREWEI |
| R1-2007672 | RRM relaxation for Reduced Capability NR devices | vivo, Guangdong Genius |
| R1-2007719 | Access control and identification for Reduced Capability NR devices | ZTE |
| R1-2007866 | Identification and access restriction for reduced capability NR devices | CATT |
| R1-2007951 | On identification of and access control for RedCap UEs | Intel Corporation |
| R1-2008020 | Discussion on identification and access control for Reduced Capability NR devices | CMCC |
| R1-2008052 | Other aspects for reduced capability NR devices | LG Electronics |
| R1-2008072 | Initial access for RedCap UEs | Nokia, Nokia Shanghai Bell |
| R1-2008075 | Procedure of identification for Reduced Capability NR devices | TCL Communication Ltd. |
| R1-2008088 | Discussion on the access control and configuration for reduced capability device | Xiaomi |
| R1-2008106 | Consideration on power saving for reduced capability NR devices | Spreadtrum Communications |
| R1-2008174 | UE identification and access barring | Samsung |
| R1-2008264 | Other considerations for reduced UE capability | OPPO |
| R1-2008291 | On RedCap device identification | Panasonic |
| R1-2008329 | Other aspects for reduced capability devices | Huawei, HiSilicon |
| R1-2008337 | Narrowband operation and identification of RedCap UE | Lenovo, Motorola Mobility |
| R1-2008397 | Identification and access restriction for reduced capability UEs | Sharp |
| R1-2008556 | Discussion on UE identification for RedCap | NTT DOCOMO, INC. |
| R1-2008585 | Discussion on identification of reduced capability UE | ASUSTeK |
| R1-2008688 | Device identification and access restriction for RedCap | InterDigital, Inc. |
| R1-2008838 | Identification and access restriction for reduced capability NR devices | CATT |
| R1-2009317 | Moderator summary on RedCap - Others | Moderator (Intel) |
| R1-2009404 | Moderator summary#2 on RedCap - Others | Moderator (Intel) |
| R1-2009608 | Moderator summary#3 on RedCap - Others | Moderator (Intel) |
| R1-2009735 | Moderator summary#4 on RedCap - Others | Moderator (Intel) |
| R1-2009771 | Moderator summary#5 on RedCap - Others | Moderator (Intel) |
| R1-2009780 | Moderator summary#6 on RedCap - Others | Moderator (Intel) |
| 8.7.1.1 | Potential paging enhancements | |
| R1-2007600 | Paging enhancement(s) for UE power saving in IDLE/inactive mode | Huawei, HiSilicon |
| R1-2007673 | Paging enhancements for idle/inactive mode UE power saving | vivo |
| R1-2007867 | Paging enhancement for UE power saving | CATT |
| R1-2007890 | Potential paging enhancements | TCL Communication Ltd. |
| R1-2007898 | Paging enhancement for power saving | Beijing Xiaomi Software Tech |
| R1-2007971 | Discussion on power saving enhancements for paging | ZTE |
| R1-2008021 | Discussion on paging enhancement | CMCC |
| R1-2008053 | Discussion on potential paging enhancements | LG Electronics |
| R1-2008103 | Discussion on potential paging enhancements | Spreadtrum Communications |
| R1-2008175 | Discussion on paging enhancements | Samsung |
| R1-2008265 | Further discussion on Paging enhancements for power saving | OPPO |
| R1-2008287 | Potential paging enhancements for idle/inactive-mode UE power saving | Panasonic |
| R1-2008368 | Paging enhancement for idle/inactive mode UE | Sony |
| R1-2008474 | Paging enhancements for idle/inactive-mode UE power saving | Apple |
| R1-2008689 | Paging enhancements for UE power saving | InterDigital, Inc. |
| R1-2008933 | On paging enhancements for UE power saving | Nokia, Nokia Shanghai Bell |
| R1-2008964 | Paging enhancements for idle/inactive-mode UE power saving | MediaTek Inc. |
| R1-2008972 | Paging enhancements for idle/inactive-mode UE power saving | MediaTek Inc. |
| R1-2008992 | On paging enhancements for UE power saving | Intel Corporation |
| R1-2009105 | Paging enhancement for UE power saving | Lenovo, Motorola Mobility |
| R1-2009187 | Discussion on paging enhancements | NTT DOCOMO, INC. |
| R1-2009200 | Discussion on potential paging enhancements for UE power savings | Ericsson |
| R1-2009266 | Paging enhancements and evaluation methodology | Qualcomm Incorporated |
| R1-2009488 | On paging enhancements for UE power saving | Intel Corporation |
| R1-2009753 | Summary for Potential Paging Enhancements | Moderator (MediaTek) |
| R1-2009754 | Draft LS on Paging Enhancement | MediaTek Inc. |
| R1-2009801 | LS on Paging Enhancement | RAN1, MediaTek Inc. |
| 8.7.1.2 | TRS/CSI-RS occasion(s) for idle/inactive UEs | |
| R1-2007601 | Assistance RS occasions for IDLE/inactive mode | Huawei, HiSilicon |
| R1-2007674 | TRS/CSI-RS occasion(s) for idle/inactive UEs | vivo |
| R1-2007868 | Configuration of TRS/CSI-RS for paging enhancement | CATT |
| R1-2007891 | TRS/CSI-RS occasion(s) for idle/inactive UEs | TCL Communication Ltd. |
| R1-2007899 | TRS CSI-RS occasion(s) for idle inactive UEs | Beijing Xiaomi Software Tech |
| R1-2007972 | Reference signal for RRC idle and inactive UEs | ZTE |
| R1-2008022 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive-mode UEs | CMCC |
| R1-2008054 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | LG Electronics |
| R1-2008176 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive Ues | Samsung |
| R1-2008178 | Moderator summary for TRS/CSI-RS occasion(s) for idle/inactive UEs | Moderator (Samsung) |
| R1-2008266 | Further discussion on RS occasion for idle/inactive UEs | OPPO |
| R1-2008288 | Potential enhancements for TRS/CSI-RS occasion(s) for idle/inactive Ues | Panasonic |
| R1-2008369 | Considerations on TRS/CSI-RS occasion(s) for idle/inactive mode UE | Sony |
| R1-2008475 | Indication of TRS/CSI-RS for idle/inactive-mode UE power saving | Apple |
| R1-2008690 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | InterDigital, Inc. |
| R1-2008934 | On RS information to IDLE/Inactive mode Ues | Nokia, Nokia Shanghai Bell |
| R1-2008965 | On TRS/CSI-RS occasion(s) for idle/inactive mode UE power saving | MediaTek Inc. |
| R1-2008973 | On TRS/CSI-RS occasion(s) for idle/inactive mode UE power saving | MediaTek Inc. |
| R1-2008993 | Discussion on TRS/CSI-RS reception during idle/inactive mode | Intel Corporation |
| R1-2009106 | Provision of TRS/CSI-RS for idle/inactive UEs | Lenovo, Motorola Mobility |
| R1-2009151 | Consideration on TRS/CSI-RS occasion(s) for idle/inactive UEs | Spreadtrum Communications |
| R1-2009188 | Discussion on TRS/CSI-RS occasion for idle/inactive UEs | NTT DOCOMO, INC. |
| R1-2009201 | Provisioning of potential TRS/CSI-RS occasion(s) for Idle/Inactive UEs | Ericsson |
| R1-2009267 | TRS CSI-RS for idle and inactive UE power saving | Qualcomm Incorporated |
| R1-2009791 | [draft] LS on signalling method for TRS/CSI-RS occasion(s) for idle/inactive UE(s) | Samsung |
| R1-2009848 | LS on signalling method for TRS/CSI-RS occasion(s) for idle/inactive UE(s) | RAN1, Samsung |
| 8.7.1.3 | Other | |
| R1-2007675 | Discussion on paging grouping | vivo |
| R1-2007869 | Link level performance of IDLE UE for UE power saving | CATT |
| R1-2007973 | Additional simulation results of UE power consumption in RRC idle and inactive state | ZTE |
| R1-2008335 | Analysis on power consumption for IDLE mode UE | Huawei, HiSilicon |
| R1-2009202 | High-level UE energy consumption profiling | Ericsson |
| R1-2009300 | On network power consumption model | Nokia, Nokia Shanghai Bell |
| 8.7.2 | Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime | |
| R1-2007602 | Extension(s) to Rel-16 DCI-based power saving adaptation for an active BWP | Huawei, HiSilicon |
| R1-2007676 | Discussion on DCI-based power saving adaptation in connected mode | vivo |
| R1-2007701 | Extension to Rel-16 DCI-based power sabing adaptation during DRX Active Time | GDCNI |
| R1-2007870 | PDCCH monitoring adaptation | CATT |
| R1-2007974 | Extension to Rel-16 DCI-based power saving adaptation during DRX Active Time | ZTE |
| R1-2008023 | Discussion on PDCCH monitoring reduction during DRX active time | CMCC |
| R1-2008055 | Discussion on DCI-based power saving adaptation during DRX ActiveTime | LG Electronics |
| R1-2008177 | Discussion on DCI-based power saving techniques | Samsung |
| R1-2008267 | Discussion on DCI-based power saving adaptation | OPPO |
| R1-2008289 | Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime | Panasonic |
| R1-2008476 | Enhanced DCI-based power saving adapation | Apple |
| R1-2008691 | PDCCH-based power saving signal design considerations | InterDigital, Inc. |
| R1-2008711 | DCI-based Power Saving Enhancements | Fraunhofer HHI, Fraunhofer IIS |
| R1-2008714 | Power saving adaptation during Active Time | ASUSTeK |
| R1-2008935 | UE power saving enhancements for Active Time | Nokia, Nokia Shanghai Bell |
| R1-2008966 | Discussion on DCI-based power saving adaptation during DRX active time | MediaTek Inc. |
| R1-2008974 | Discussion on DCI-based power saving adaptation during DRX active time | MediaTek Inc. |
| R1-2008994 | On PDCCH monitoring reduction techniques during active time | Intel Corporation |
| R1-2009056 | Discussion on extension(s) to Rel-16 DCI-based power saving adaptation | Asia Pacific Telecom co. Ltd |
| R1-2009107 | Enhanced DCI based power saving adaptation | Lenovo, Motorola Mobility |
| R1-2009150 | Discussion on power saving techniques for connected-mode UE | Spreadtrum Communications |
| R1-2009189 | Discussion on extension to DCI-based power saving adaptation | NTT DOCOMO, INC. |
| R1-2009203 | Discussion on potential enhancements for power savings during active time | Ericsson |
| R1-2009268 | DCI-based power saving adaptation during DRX ActiveTime | Qualcomm Incorporated |
| R1-2009299 | On power saving adaptation during the DRX active time | Sony |
| R1-2009378 | On PDCCH monitoring reduction techniques during active time | Intel Corporation |
| R1-2009501 | FL summary#1 of power saving for Active Time | Moderator (vivo) |
| R1-2009655 | FL summary#2 of power saving for Active Time | Moderator (vivo) |
| R1-2009656 | FL summary#3 of power saving for Active Time | Moderator (vivo) |
| R1-2009804 | FL summary#4 of power saving for Active Time | Moderator (vivo) |
| 8.7.3 | Other | |
| R1-2007677 | Discussion on RAN2 and RAN4 related power saving relaxation | vivo |
| R1-2007871 | Feature interaction between Secondary DRX group and DCP/SCell dormancy | CATT |
| R1-2007975 | Further discussion on potential power saving schemes for RRC connected UEs | ZTE |
| R1-2008268 | Discussion on RLM relaxation | OPPO |
| R1-2008330 | Other considerations on power saving in Rel-17 | Huawei, HiSilicon |
| R1-2008477 | Power saving evaluation for RLM/BFD relaxation | Apple |
| R1-2009204 | Evaluation of additional UE power saving schemes | Ericsson |
| 8.8 | Study on NR coverage enhancement | |
| R1-2007992 | TR 38.830 v0.0.3 Study on NR coverage enhancements | China Telecom |
| R1-2009461 | TR 38.830 v0.1.0 Study on NR coverage enhancements | China Telecom |
| R1-2009851 | TR 38.830 v0.2.0 Study on NR coverage enhancements | China Telecom |
| R1-2009852 | [103-e-NR-CovEnh-01] Summary of email discussion on TR38.830 update | Moderator (China Telecom) |
| 8.8.1 | Baseline coverage performance using LLS | |
| R1-2009808 | [103-e-NR-CovEnh-EvaluationResults]: Summary of simulation results for baseline | Moderator (SoftBank, Nokia) |
| 8.8.1.1 | FR1 | |
| R1-2007581 | Evaluation on the baseline performance for FR1 | Huawei, HiSilicon |
| R1-2007678 | Evaluation on NR coverage performance for FR1 | vivo |
| R1-2007741 | Discussion on baseline coverage performance for FR1 | ZTE |
| R1-2007872 | Baseline coverage performance for FR1 | CATT |
| R1-2007904 | Baseline coverage performance for uplink in FR1 | Indian Institute of Tech (H) |
| R1-2007931 | FR1 PUSCH Baseline Coverage Performance | Sierra Wireless, S.A. |
| R1-2007952 | On baseline coverage performance for FR1 | Intel Corporation |
| R1-2007993 | Updated baseline performance for NR coverage enhancements for FR1 | China Telecom |
| R1-2008024 | Discussion on the baseline performance in FR1 | CMCC |
| R1-2008089 | Baseline coverage performance for FR1 | Xiaomi |
| R1-2008179 | Baseline coverage performance using LLS for FR1 | Samsung |
| R1-2008269 | Evaluation on NR coverage performance for FR1 | OPPO |
| R1-2008343 | Link and System Evaluation of Coverage for FR1 | Ericsson |
| R1-2008377 | Baseline coverage performance analysis in FR1 | Panasonic Corporation |
| R1-2008380 | Target value for FR1 voice coverage enhancements | SoftBank Corp. |
| R1-2008398 | Link budget analysis for FR1 | Sharp |
| R1-2008478 | Evaluation on FR1 coverage performance | Apple |
| R1-2008481 | FR1 baseline coverage performance using LLS | InterDigital, Inc. |
| R1-2008515 | Discussion on scenarios for FR1 baseline performance evaluation | MediaTek Inc. |
| R1-2008557 | Baseline coverage performance for FR1 | NTT DOCOMO, INC. |
| R1-2008624 | Baseline FR1 coverage performance | Qualcomm Incorporated |
| R1-2008701 | Baseline coverage evaluation of UL and DL channels – FR1 | Nokia, Nokia Shanghai Bell |
| R1-2009169 | FR1 baseline coverage performance using LLS | InterDigital, Inc. |
| R1-2009316 | Baseline FR1 coverage performance | Qualcomm Incorporated |
| R1-2009341 | Summary #1 on A.I. 8.8.1.1 baseline coverage performance using LLS for FR1 | Moderator (SoftBank) |
| R1-2009568 | Evaluation on the baseline performance for FR1 | Huawei, HiSilicon |
| R1-2009582 | Baseline coverage performance analysis in FR1 | Panasonic Corporation |
| R1-2009617 | Link budget analysis for FR1 | Sharp |
| R1-2009727 | Link and System Evaluation of Coverage for FR1 | Ericsson |
| R1-2009809 | Summary of [103-e-NR-CovEnh-02] A.I. 8.8.1.1 baseline coverage performance using LLS for FR1 | Source: Moderator (SoftBank) |
| 8.8.1.2 | FR2 | |
| R1-2007582 | Evaluation on the baseline performance for FR2 | Huawei, HiSilicon |
| R1-2007679 | Evaluation on NR coverage performance for FR2 | vivo |
| R1-2007742 | Discussion on baseline coverage performance for FR2 | ZTE |
| R1-2007873 | Baseline coverage performance for FR2 | CATT |
| R1-2007953 | On baseline coverage performance for FR2 | Intel Corporation |
| R1-2008025 | Discussion on the baseline performance in FR2 | CMCC |
| R1-2008090 | Evaluation on NR coverage performance for FR2 | Xiaomi |
| R1-2008180 | Baseline coverage performance using LLS for FR2 | Samsung |
| R1-2008270 | Evaluation on NR coverage performance for FR2 | OPPO |
| R1-2008344 | Link and System Evaluation of Coverage for FR2 | Ericsson |
| R1-2008482 | FR2 baseline coverage performance using LLS | InterDigital, Inc. |
| R1-2008558 | Baseline coverage performance for FR2 | NTT DOCOMO, INC. |
| R1-2008625 | Baseline FR2 coverage performance | Qualcomm Incorporated |
| R1-2008702 | Baseline coverage evaluation of UL and DL channels – FR2 | Nokia, Nokia Shanghai Bell |
| R1-2009170 | FR2 baseline coverage performance using LLS | InterDigital, Inc. |
| R1-2009342 | Summary of A.I. 8.8.1.2 - Baseline coverage performance using LLS for FR2 | Moderator (Nokia) |
| R1-2009794 | Link and System Evaluation of Coverage for FR2 | Ericsson |
| R1-2009797 | Summary on AI 8.8.1.2 baseline coverage performance using LLS for FR2 | Nokia, Nokia Shanghai Bell |
| 8.8.2 | Potential techniques for coverage enhancements | |
| R1-2009719 | [103-e-NR-CovEnh-EvaluationResults]: Summary of simulation results for enhancements | Moderator (China Telecom) |
| 8.8.2.1 | PUSCH coverage enhancement | |
| R1-2007583 | Potential solutions for PUSCH coverage enhancement | Huawei, HiSilicon |
| R1-2007640 | PUSCH coverage enhancement | Beijing Xiaomi Mobile Software |
| R1-2007680 | Discussion on Solutions for PUSCH coverage enhancement | vivo |
| R1-2007743 | Discussion on potential techniques for PUSCH coverage enhancements | ZTE |
| R1-2007874 | Discussion on potential techniques for PUSCH coverage enhancement | CATT |
| R1-2007905 | PUSCH coverage enhancements | Indian Institute of Tech (H) |
| R1-2007930 | Potential techniques for NR coverage enhancements | Sierra Wireless, S.A. |
| R1-2007954 | On potential techniques for PUSCH coverage enhancement | Intel Corporation |
| R1-2007989 | PUSCH coverage enhancement | ETRI |
| R1-2007994 | Discussion on PUSCH coverage enhancements | China Telecom |
| R1-2008026 | Discussion on the PUSCH coverage enhancement | CMCC |
| R1-2008078 | Discussion on PUSCH coverage enhancement | NEC |
| R1-2008092 | Potential solutions for PUSCH coverage enhancement | Spreadtrum Communications |
| R1-2008181 | PUSCH coverage enhancement | Samsung |
| R1-2008271 | Consideration on PUSCH coverage enhancement | OPPO |
| R1-2008370 | On PUSCH coverage enhancement techniques | Sony |
| R1-2008378 | Discussion on PUSCH coverage enhancements | Panasonic Corporation |
| R1-2008399 | PUSCH coverage enhancement | Sharp |
| R1-2008403 | Discussions on PUSCH coverage enhancement | LG Electronics |
| R1-2008419 | PUSCH coverage enhancement | Ericsson |
| R1-2008479 | On potential techniques for PUSCH coverage enhancement | Apple |
| R1-2008483 | PUSCH coverage enhancements | InterDigital, Inc. |
| R1-2008559 | Potential techniques for PUSCH coverage enhancements | NTT DOCOMO, INC. |
| R1-2008626 | Potential coverage enhancement techniques for PUSCH | Qualcomm Incorporated |
| R1-2008700 | On the use of Tx diversity in DFT-s-OFDM for PUSCH coverage enhancement | NICT |
| R1-2008703 | Discussion on approaches and solutions for NR PUSCH coverage enhancement | Nokia, Nokia Shanghai Bell |
| R1-2008729 | Discussion on potential techniques for PUSCH coverage enhancement | WILUS Inc. |
| R1-2008743 | On transmit diversity techniques for PUSCH coverage enhancement | Mitsubishi Electric RCE |
| R1-2008874 | Discussion on PUSCH coverage enhancements | China Telecom |
| R1-2008895 | PUSCH coverage enhancement | Samsung |
| R1-2009168 | PUSCH coverage enhancements | InterDigital, Inc. |
| R1-2009320 | FL summary of PUSCH coverage enhancements | Moderator (China Telecom) |
| R1-2009583 | PUSCH coverage enhancements | InterDigital, Inc. |
| R1-2009647 | PUSCH coverage enhancement | Samsung |
| R1-2009729 | Potential coverage enhancement techniques for PUSCH | Qualcomm Incorporated |
| R1-2009792 | Discussion on approaches and solutions for NR PUSCH coverage enhancement | Nokia, Nokia Shanghai Bell |
| R1-2009814 | [103-e-NR-CovEnh-04] Summary of email discussion on PUSCH coverage enhancements | Moderator (China Telecom) |
| 8.8.2.2 | PUCCH coverage enhancement | |
| R1-2007584 | Potential solutions for PUCCH coverage enhancement | Huawei, HiSilicon |
| R1-2007681 | Discussion on Solutions for PUCCH coverage enhancement | vivo |
| R1-2007744 | Discussion on potential techniques for PUCCH coverage enhancements | ZTE |
| R1-2007875 | Discussion on potential techniques for PUCCH coverage enhancement | CATT |
| R1-2007955 | On potential techniques for PUCCH coverage enhancement | Intel Corporation |
| R1-2007995 | Discussion on PUCCH coverage enhancements | China Telecom |
| R1-2008027 | Discussion on PUCCH coverage enhancement | CMCC |
| R1-2008079 | Discussion on PUCCH coverage enhancement | NEC |
| R1-2008182 | PUCCH coverage enhancement | Samsung |
| R1-2008272 | PUCCH coverage enhancement schemes | OPPO |
| R1-2008371 | On PUCCH coverage enhancement techniques | Sony |
| R1-2008379 | Discussion on PUCCH coverage enhancements | Panasonic Corporation |
| R1-2008400 | PUCCH coverage enhancement | Sharp |
| R1-2008404 | Discussions on PUCCH coverage enhancement | LG Electronics |
| R1-2008420 | PUCCH coverage enhancement | Ericsson |
| R1-2008484 | PUCCH coverage enhancements | InterDigital, Inc. |
| R1-2008560 | Potential techniques for PUCCH coverage enhancements | NTT DOCOMO, INC. |
| R1-2008627 | Potential coverage enhancement techniques for PUCCH | Qualcomm Incorporated |
| R1-2008704 | Discussion on approaches and solutions for NR PUCCH coverage enhancement | Nokia, Nokia Shanghai Bell |
| R1-2008730 | Discussion on potential techniques for PUCCH coverage enhancement | WILUS Inc. |
| R1-2008756 | PUCCH coverage enhancements | Indian Institute of Tech (H) |
| R1-2008759 | Low-PAPR Sequence-Based Approaches for PUCCH Coverage Enhancement | EURECOM |
| R1-2008938 | Low-PAPR Sequence-Based Approaches for PUCCH Coverage Enhancement | EURECOM |
| R1-2008942 | Discussion on Solutions for PUCCH coverage enhancement | vivo Mobile Communication (S) |
| R1-2009315 | Potential coverage enhancement techniques for PUCCH | Qualcomm Incorporated |
| R1-2009321 | FL summary of PUCCH coverage enhancement | Moderator (Qualcomm) |
| R1-2009360 | Potential coverage enhancement techniques for PUCCH | Qualcomm Incorporated |
| R1-2009405 | FL summary#2 of PUCCH coverage enhancement | Moderator (Qualcomm) |
| R1-2009451 | Low-PAPR Sequence-Based Approaches for PUCCH Coverage Enhancement | EURECOM |
| R1-2009552 | Potential coverage enhancement techniques for PUCCH | Qualcomm Incorporated |
| R1-2009602 | On potential techniques for PUCCH coverage enhancement | Intel Corporation |
| R1-2009648 | Discussion on Solutions for PUCCH coverage enhancement | vivo Mobile Communication |
| R1-2009696 | Discussion on potential techniques for PUCCH coverage enhancements | ZTE |
| R1-2009711 | Potential coverage enhancement techniques for PUCCH | Qualcomm Incorporated |
| R1-2009737 | PUCCH DTX detection performance | Ericsson |
| R1-2009747 | Potential solutions for PUCCH coverage enhancement | Huawei, HiSilicon |
| R1-2009784 | LS on PUCCH and PUSCH repetition | RAN1, Qualcomm |
| R1-2009802 | Potential coverage enhancement techniques for PUCCH | Qualcomm Incorporated |
| 8.8.2.3 | Coverage enhancement for channels other than PUSCH and PUCCH | |
| R1-2007585 | Discussion on the potential coverage enhancement solutions for other channels | Huawei, HiSilicon |
| R1-2007682 | Discussion on coverage enhancement for channels other than PUCCH and PUSCH | vivo |
| R1-2007745 | Discussion on potential techniques for channels other than PUSCH and PUCCH | ZTE |
| R1-2007876 | Discussion on coverage enhancement for channels other than PUSCH and PUCCH | CATT |
| R1-2007906 | Coverage enhancement for Msg3 | Indian Institute of Tech (H) |
| R1-2007956 | On coverage enhancement for channels other than PUSCH and PUCCH | Intel Corporation |
| R1-2007996 | Discussion on Msg3 PUSCH enhancements | China Telecom |
| R1-2008028 | Discussion on coverage enhancement for channels other than PUSCH and PUCCH | CMCC |
| R1-2008080 | Discussion on Msg3 coverage enhancement | NEC |
| R1-2008183 | Coverage enhancement for channels other than PUSCH and PUCCH | Samsung |
| R1-2008273 | Coverage enhancement on NR channels other than PUSCH and PUCCH | OPPO |
| R1-2008310 | Coverage Enhancements for initial access | AT&T |
| R1-2008372 | Coverage enhancement for initial access | Sony |
| R1-2008401 | Coverage enhancement for channels other than PUCCH/PUSCH | Sharp |
| R1-2008405 | Discussions on coverage enhancement for channels other than PUSCH and PUCCH | LG Electronics |
| R1-2008421 | Coverage enhancement for channels other than PUSCH and PUCCH | Ericsson |
| R1-2008480 | Discussion on Msg3 coverage enhancement | Apple |
| R1-2008485 | Coverage enhancements for initial access | InterDigital, Inc. |
| R1-2008561 | Potential techniques for coverage enhancement for channels other than PUSCH and PUCCH | NTT DOCOMO, INC. |
| R1-2008628 | Potential coverage enhancement techniques for other channels | Qualcomm Incorporated |
| R1-2008705 | Discussion on approaches and solutions for NR coverage enhancement: other channels than PUSCH and PUCCH | Nokia, Nokia Shanghai Bell |
| R1-2008716 | Potential techniques for Msg3 PUSCH coverage enhancement | Potevio |
| R1-2008731 | Discussion on potential techniques for coverage enhancement for channels other than PUSCH and PUCCH | WILUS Inc. |
| R1-2009226 | Potential coverage enhancement techniques for other channels | Qualcomm Incorporated |
| R1-2009309 | Potential coverage enhancement techniques for other channels | Qualcomm Incorporated |
| R1-2009322 | Feature lead summary on coverage enhancement for channels other than PUSCH and PUCCH | Moderator (ZTE) |
| R1-2009793 | Discussion on approaches and solutions for NR coverage enhancement: other channels than PUSCH and PUCCH | Nokia, Nokia Shanghai Bell |
| R1-2009805 | Feature lead summary#2 on coverage enhancement for channels other than PUSCH and PUCCH | Moderator (ZTE) |
| 8.8.3 | Other | |
| R1-2007683 | Considerations on Parameters for Coverage Evaluation | vivo |
| R1-2007746 | Discussion on target performance for NR coverage enhancements | ZTE |
| R1-2007877 | Discussion on remaining issues for coverage enhancement | CATT |
| R1-2007957 | On simulation assumptions for NR coverage enhancement | Intel Corporation |
| R1-2008274 | Functionality of Coverage Enhancement and other WI | OPPO |
| R1-2008422 | Coverage Parameter Sensitivity and Network Enhancement | Ericsson |
| R1-2008487 | Discussion on simulation assumptions for VoIP | InterDigital, Inc. |
| R1-2008629 | Other coverage enhancement aspects | Qualcomm Incorporated |
| R1-2008706 | Evaluation assumptions for NR coverage enhancement evaluation | Nokia, Nokia Shanghai Bell |
| 8.9 | Rel-17 enhancements for NB-IoT and LTE-MTC | |
| R1-2009836 | Session notes for 8.9 (Rel-17 enhancements for NB-IoT and LTE-MTC) | Ad-hoc Chair (Samsung) |
| 8.9.1 | Support of 16-QAM for unicast in UL and DL for NB-IoT | |
| R1-2007618 | Support of 16QAM for unicast in UL and DL in NB-IoT | Huawei, HiSilicon |
| R1-2008073 | Support of 16-QAM for NB-IoT | Nokia, Nokia Shanghai Bell |
| R1-2008697 | Discussion on UL and DL 16QAM for NB-IoT | ZTE |
| R1-2008920 | Support 16QAM for NBIoT | Lenovo, Motorola Mobility |
| R1-2008930 | Support of 16-QAM for unicast in UL and DL in NB-IoT | Ericsson |
| R1-2008969 | Further considerations on support of 16QAM for NB-IOT | MediaTek Inc. |
| R1-2009112 | Support of 16-QAM for NB-IoT | Qualcomm Incorporated |
| R1-2009125 | Design considerations to support 16-QAM for NB-IOT | Sierra Wireless, S.A. |
| R1-2009477 | Feature lead summary #1 on [103-e-LTE-Rel17_NB_IoT_eMTC-01] | Moderator (Huawei) |
| R1-2009658 | Feature lead summary #2 on [103-e-LTE-Rel17_NB_IoT_eMTC-01] | Moderator (Huawei) |
| R1-2009730 | Feature lead summary #3 on [103-e-LTE-Rel17_NB_IoT_eMTC-01] | Moderator (Huawei) |
| 8.9.2 | Support additional PDSCH scheduling delay for introduction of 14-HARQ processes in DL for eMTC | |
| R1-2007619 | Support of 14-HARQ processes in DL for HD-FDD MTC UEs | Huawei, HiSilicon |
| R1-2008074 | Support of 14-HARQ processes in DL for eMTC | Nokia, Nokia Shanghai Bell |
| R1-2008698 | Support additional PDSCH scheduling delay for introduction of 14-HARQ processes in DL for eMTC | ZTE |
| R1-2008931 | Support of 14 HARQ processes in DL in LTE-MTC | Ericsson, Telefónica, Verizon, SoftBank, AT&T, Telstra |
| R1-2009113 | Support of 14 HARQ processes and scheduling delay | Qualcomm Incorporated |
| R1-2009124 | Design considerations to support 14-HARQ Feature for LTE-M | Sierra Wireless, S.A. |
| R1-2009513 | Feature Lead Summary [103-e-LTE-Rel17_NB_IoT_eMTC-02] | Moderator (Ericsson) |
| R1-2009514 | Feature Lead Summary#2 [103-e-LTE-Rel17_NB_IoT_eMTC-02] | Moderator (Ericsson) |
| R1-2009515 | Feature Lead Summary#3 [103-e-LTE-Rel17_NB_IoT_eMTC-02] | Moderator (Ericsson) |
| 8.9.3 | Other | |
| R1-2007620 | Channel quality reporting in NB-IoT to support 16QAM | Huawei, HiSilicon |
| R1-2008699 | DL TBS increase for eMTC | ZTE |
| R1-2008932 | On the support of a maximum DL TBS of 1736 bits in LTE-MTC | Ericsson |
| 8.10 | Enhancements to Integrated Access and Backhaul | |
| R1-2009837 | Session notes for 8.10 (Enhancements to Integrated Access and Backhaul) | Ad-hoc Chair (Samsung) |
| 8.10.1 | Enhancements to resource multiplexing between child and parent links of an IAB node | |
| R1-2007594 | Resource multiplexing between backhaul and access for IAB duplexing enhancements | Huawei, HiSilicon |
| R1-2007684 | Enhancement to resource multiplexing between child and parent links | vivo |
| R1-2008029 | Discussion on resource multiplexing in the simultaneous operation | CMCC |
| R1-2008184 | Enhancements to Resource Multiplexing for NR IAB | Samsung |
| R1-2008312 | Enhancements for IAB resource multiplexing | AT&T |
| R1-2008406 | Discussions on IAB resource multiplexing enhancements | LG Electronics |
| R1-2008858 | Enhancements to the IAB resource multiplexing | ZTE, Sanechips |
| R1-2008863 | Enhancements for resource multiplexing among IAB backhaul and access links | Nokia, Nokia Shanghai Bell |
| R1-2008995 | Enhancements to Resource Multiplexing between Child and Parent Links of an IAB Node | Intel Corporation |
| R1-2009018 | Enhancements to resource multiplexing between child and parent links of an IAB node | ETRI |
| R1-2009108 | Enhancements to resource multiplexing for IAB | Lenovo, Motorola Mobility |
| R1-2009190 | Resource multiplexing between child and parent links of an IAB node | NTT DOCOMO, INC. |
| R1-2009220 | Discussion on IAB resource multiplexing enhancements | ETRI |
| R1-2009221 | Discussions on enhancements to resource multiplexing between child and parent links of an IAB node | CEWiT |
| R1-2009269 | Resource management for enhanced duplexing | Qualcomm Incorporated |
| R1-2009301 | Resource multiplexing and DC in enhanced IAB | Ericsson |
| R1-2009604 | Summary #1 of [103-e-NR-eIAB-01] | Moderator (AT&T) |
| R1-2009734 | Summary #2 of [103-e-NR-eIAB-01] | Moderator (AT&T) |
| 8.10.2 | Other enhancements for simultaneous operation of IAB-node’s child and parent links | |
| R1-2007595 | Enhancements for simultaneous operation of MT and DU | Huawei, HiSilicon |
| R1-2007685 | Other enhancements for simultaneous operation of child and parent links | vivo |
| R1-2007786 | Other enhancements for simultaneous operation of IAB-node’s child and parent links | Fujitsu |
| R1-2008030 | Discussion on the enhancement for simultaneous operation | CMCC |
| R1-2008185 | Enhancements to Timing, Power Control and CLI for NR IAB | Samsung |
| R1-2008313 | Enhancements for IAB interference management | AT&T |
| R1-2008407 | Discussions on other enhancements for simultaneous operation | LG Electronics |
| R1-2008816 | Discussion on simultaneous operation of IAB-node’s child and parent links | CEWiT |
| R1-2008859 | Enhancements for simultaneous operation of child and parent links | ZTE, Sanechips |
| R1-2008864 | Other enhancements for simultaneous operation of IAB Parent and Child | Nokia, Nokia Shanghai Bell |
| R1-2008996 | Power Control Enhancements for Simultaneous Operations | Intel Corporation |
| R1-2009019 | Discussion on simultaneous operation enhancements | ETRI |
| R1-2009109 | Enhancements for simultaneous operation in IAB systems | Lenovo, Motorola Mobility |
| R1-2009137 | Power Control: Subsequent Contribution | Sharp |
| R1-2009191 | Other enhancements for simultaneous operation of IAB-node’s child and parent links | NTT DOCOMO, INC. |
| R1-2009270 | On enhancements for simultaneous operation of IAB-node's child and parent links | Qualcomm Incorporated |
| R1-2009302 | Timing, CLI and power control in enhanced IAB | Ericsson |
| R1-2009567 | Summary #1 of [103-e-NR-eIAB-02] | Moderator (Qualcomm) |
| R1-2009709 | Summary #2 of [103-e-NR-eIAB-02] | Moderator (Qualcomm) |
| R1-2009765 | Summary #3 of [103-e-NR-eIAB-02] | Moderator (Qualcomm) |
| 8.10.3 | Other | |
| R1-2007686 | Other enhancements to Rel-17 IAB nodes | vivo |
| R1-2008314 | Performance of simultaneous operation of IAB-node’s child and parent links | AT&T |
| R1-2008327 | Other enhancements for IAB | Huawei, HiSilicon |
| R1-2008408 | Discussion on RACH procedure for IAB enhancement | LG Electronics |
| R1-2008860 | Discussion on multiplexing capability for IAB | ZTE, Sanechips |
| R1-2009020 | Other enhancements to IAB | ETRI |
| R1-2009303 | Refined beam calibration in enhanced IAB | Ericsson |
| 8.11 | NR Sidelink enhancement | |
| R1-2008186 | On Sidelink Enhacement Work Item | Samsung |
| 8.11.1 | Remaining issues for sidelink evaluation methodology update for power saving | |
| R1-2007614 | Sidelink evaluation methodology update for power saving | Huawei, HiSilicon |
| R1-2007621 | Discussion of remaining issues for sidelink evaluation methodology update for power saving | Nokia, Nokia Shanghai Bell |
| R1-2007687 | Discussion on sidelink evaluation methodology | vivo |
| R1-2007832 | Discussion on sidelink evaluation methodology for power saving | CATT |
| R1-2007894 | Discussion on remaining aspects of sidelink evaluation methodology update for power saving | LG Electronics |
| R1-2008187 | On Sidelink Evaluation Methodology Updates for Power Saving | Samsung |
| R1-2008238 | Discussion on evaluation methodology for SL power saving | OPPO |
| R1-2008445 | Discussion on Sidelink Power Consumption Model | Apple |
| R1-2008877 | Analysis on remaining issues for sidelink evaluation methodology | ZTE Corporation, Sanechips |
| R1-2008916 | Discussion on sidelink evaluation methodology update for power saving | Lenovo, Motorola Mobility |
| R1-2008970 | Remaining issues for sidelink evaluation methodology | MediaTek Inc. |
| R1-2008997 | Remaining issues for sidelink evaluation methodology update for power saving | Intel Corporation |
| R1-2009036 | Discussion on remaining issues of sidelink evaluation methodology update | Xiaomi |
| R1-2009071 | Remaining evaluation assumptions and methodology for power saving | Ericsson |
| R1-2009120 | V2X evaluation methodology and channel model updates | InterDigital, Inc. |
| R1-2009192 | Remainig issues on sidelink evaluation methodology for power saving | NTT DOCOMO, INC. |
| R1-2009271 | Evaluation Methodology for Power Saving in Sidelink | Qualcomm Incorporated |
| R1-2009787 | Feature lead summary for AI 8.11.1 Remaining issues for sidelink evaluation methodology update for power saving | Moderator(LG Electronics) |
| 8.11.2 | Resource allocation enhancement | |
| R1-2007878 | Discussion on enhancement for NR V2X Mode 2 | ITRI |
| R1-2008188 | On Resource Allocation Enhacements | Samsung |
| 8.11.2.1 | Resource allocation for power saving | |
| R1-2007553 | Power consumption reduction for sidelink resource allocation | FUTUREWEI |
| R1-2007615 | Sidelink resource allocation to reduce power consumption | Huawei, HiSilicon |
| R1-2007622 | Discussion of resource allocation for power saving | Nokia, Nokia Shanghai Bell |
| R1-2007688 | Resource allocation for sidelink power saving | vivo |
| R1-2007787 | Considerations on partial sensing in NR V2X | Fujitsu |
| R1-2007833 | Discussion on resource allocation for power saving | CATT |
| R1-2007879 | Discussion on sidelink resource allocation for power saving | ITRI |
| R1-2007892 | Resource allocation for power saving | TCL Communication Ltd. |
| R1-2007895 | Discussion on resource allocation for power saving | LG Electronics |
| R1-2008031 | Discussion on resource allocation for power saving | CMCC |
| R1-2008098 | Discussion on sidelink resource allocation for power saving | Spreadtrum Communications |
| R1-2008189 | On Resource Allocation for Power Saving | Samsung |
| R1-2008239 | Power saving mechanism in NR sidelink | OPPO |
| R1-2008373 | Discussion on sidelink resource allocation for power saving | Sony |
| R1-2008446 | Discussion on Resource Allocation for Power Saving | Apple |
| R1-2008817 | NR Sidelink Resource Allocation for UE Power Saving | Fraunhofer IIS, Fraunhofer HHI |
| R1-2008836 | Discussion on Sidelink Resource Allocation for Power Saving | Panasonic Corporation |
| R1-2008878 | Discussion on resource allocation for power saving | ZTE Corporation, Sanechips |
| R1-2008917 | Sidelink resource allocation for Power saving | Lenovo, Motorola Mobility |
| R1-2008950 | Discussion on resource allocation for power saving | NEC |
| R1-2008971 | Resource allocation for sidelink power saving | MediaTek Inc. |
| R1-2008998 | Potential sidelink enhancements for UE power saving | Intel Corporation |
| R1-2009021 | Discussion on resource allocation for power saving | ETRI |
| R1-2009037 | Discussion on sidelink resource allocation for power saving | Xiaomi |
| R1-2009072 | Resource allocation mechanisms for power saving | Ericsson |
| R1-2009079 | Considerations on partial sensing in NR V2X | CAICT |
| R1-2009121 | Sidelink resource allocation for power saving | InterDigital, Inc. |
| R1-2009128 | Sidelink resource allocation to reduce power consumption | ROBERT BOSCH GmbH |
| R1-2009138 | Discussion on resource allocation for power saving | Sharp |
| R1-2009161 | On Resource Allocation Power Saving Enhancement for NR Sidelink | Convida Wireless |
| R1-2009193 | Discussion on sidelink resource allocation for power saving | NTT DOCOMO, INC. |
| R1-2009222 | Resource allocation for power saving with partial sensing in NR sidelink enhancement | ITL, KRRI |
| R1-2009272 | Power Savings for Sidelink | Qualcomm Incorporated |
| R1-2009287 | Views on power saving for NR sidelink enhancement | KT Corp. |
| R1-2009584 | FL summary for AI 8.11.2.1 – resource allocation for power saving | Source: Moderator (OPPO) |
| 8.11.2.2 | Feasibility and benefits for mode 2 enhancements | |
| R1-2007554 | Views on resource allocation enhancements for sidelink communication | FUTUREWEI |
| R1-2007616 | Inter-UE coordination in sidelink resource allocation | Huawei, HiSilicon |
| R1-2007623 | Discussion of feasibility and benefits for mode 2 enhancements | Nokia, Nokia Shanghai Bell |
| R1-2007689 | Discussion on mode-2 enhancements | vivo |
| R1-2007771 | Inter-UE Coordination Mode 2 | Kyocera Corporation |
| R1-2007788 | Considerations on inter-UE coordination for mode 2 enhancements | Fujitsu |
| R1-2007834 | Discussion on feasibility and benefits for mode 2 enhancements | CATT |
| R1-2007880 | Enhancement of Mode 2 Latency Performance | ITRI |
| R1-2007893 | Feasibility and benefits for mode 2 enhancements | TCL Communication Ltd. |
| R1-2007896 | Discussion on feasibility and benefits for mode 2 enhancements | LG Electronics |
| R1-2008032 | Discussion on reliability and latency enhancements for mode-2 resource allocation | CMCC |
| R1-2008099 | Discussion on feasibility and benefit of mode 2 enhancements | Spreadtrum Communications |
| R1-2008190 | On Feasibility and Benefits for Mode2 Enhancements | Samsung |
| R1-2008240 | Inter-UE coordination in mode 2 of NR sidelink | OPPO |
| R1-2008374 | Discussion on reliability and latency enhancements for mode 2 | Sony |
| R1-2008447 | Discussion on Inter-UE Coordination for Mode 2 Resource Allocation | Apple |
| R1-2008499 | Discussion on V2X mode 2 enhancements | ASUSTeK |
| R1-2008757 | Resource Allocation Enhancements for Mode 2 | Fraunhofer HHI, Fraunhofer IIS |
| R1-2008820 | Views on inter-UE coordination for mode 2 enhancements | Zhejiang Lab |
| R1-2008861 | Inter-UE coordination for enhanced resource allocation | Mitsubishi Electric RCE |
| R1-2008879 | Inter-UE coordination in mode-2 | ZTE Corporation, Sanechips |
| R1-2008892 | Inter-UE coordination for mode 2 enhancement | ITL |
| R1-2008918 | Sidelink resource allocation for Reliability enhancement | Lenovo, Motorola Mobility |
| R1-2008951 | Discussion on feasibility and benefits for mode 2 enhancements | NEC |
| R1-2008975 | Discussion on Mode 2 enhancements | MediaTek Inc. |
| R1-2008999 | Analysis of potential sidelink enhancements targeting Mode 2 reliability and latency | Intel Corporation |
| R1-2009022 | Discussion on feasibility and benefits for mode 2 enhancements | ETRI |
| R1-2009038 | Considerations on Mode 2 enhancement for enhanced reliability and reduced latency | Xiaomi |
| R1-2009073 | Feasibility and benefits of mode 2 enhancements for inter-UE coordination | Ericsson |
| R1-2009122 | NR SL Mode 2 enhancement for reliability improvement | InterDigital, Inc. |
| R1-2009126 | Mode 2 enhancements in sidelink | Panasonic Corporation |
| R1-2009127 | Discussion on sidelink mode-2 resource allocation enhancements | ROBERT BOSCH GmbH |
| R1-2009139 | Enhancements of resource allocation Mode 2 for NR sidelink | Sharp |
| R1-2009162 | On Resource Allocation Mode 2 Enhancement for NR Sidelink | Convida Wireless |
| R1-2009194 | Resource allocation for reliability and latency enhancements | NTT DOCOMO, INC. |
| R1-2009273 | Reliability and Latency Enhancements for Mode 2 | Qualcomm Incorporated |
| R1-2009291 | Discussion on feasibility and benefits for NR Sidelink mode 2 enhancements | CEWiT |
| R1-2009297 | Views on feasibility and benefits for mode 2 enhancements | KT Corp. |
| R1-2009319 | Inter-UE coordination in mode 2 of NR sidelink | OPPO |
| R1-2009788 | Feature lead summary for AI 8.11.2.2 Feasibility and benefits for mode 2 enhancements | Moderator(LG Electronics) |
| R1-2009841 | LS on Mode 2 enhancements in NR sidelink | RAN1, LG Electronics |
| 8.11.3 | Other | |
| R1-2007690 | Discussion on sidelink DRX | vivo |
| R1-2007881 | Discussion on NR sidelink enhancements | ITRI |
| R1-2007897 | Discussion on physical layer design considering sidelink DRX operation | LG Electronics |
| R1-2008191 | On Sidelink Issues and RAN1 Impacts | Samsung |
| R1-2008241 | The effect of DRX on resource selection | OPPO |
| R1-2008332 | Physical layer impacts of sidelink DRX | Huawei, HiSilicon |
| R1-2008448 | Discussion on Sidelink DRX | Apple |
| R1-2008500 | Discussion on SL DRX impact on physical layer | ASUSTeK |
| R1-2008758 | Other Sidelink Aspects Impacting RAN1 | Fraunhofer HHI, Fraunhofer IIS |
| R1-2008880 | Potential impact of DRX enhancement to RAN1 discussion | ZTE Corporation, Sanechips |
| R1-2008919 | Discussion on potential sidelink DRX impacts in RAN1 | Lenovo, Motorola Mobility |
| R1-2009039 | Discussion on power saving and congestion control | Xiaomi |
| R1-2009074 | On the relationship between partial sensing and DRX | Ericsson |
| R1-2009123 | On multi-carrier and DRX operation for SL | InterDigital, Inc. |
| 8.12 | NR Multicast and Broadcast Services | |
| R1-2008033 | Updated NR MBS work plan | CMCC |
| 8.12.1 | Mechanisms to support group scheduling for RRC_CONNECTED UEs | |
| R1-2007556 | Group scheduling for MC/BC services | FUTUREWEI |
| R1-2007562 | Resource configuration and group scheduling for RRC_CONNECTED UEs | Huawei, HiSilicon |
| R1-2007637 | Group scheduling for RRC_CONNECTED UEs | CHENGDU TD TECH LTD. |
| R1-2007691 | Discussion on mechanisms to support group scheduling for RRC_CONNECTED UEs | vivo |
| R1-2007835 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs in MBS | CATT |
| R1-2008034 | Discussion on group scheduling mechanisms | CMCC |
| R1-2008064 | Support of group scheduling for RRC_CONNECTED UEs | LG Electronics |
| R1-2008192 | On mechanisms to support group scheduling for RRC_CONNECTED UEs | Samsung |
| R1-2008242 | Group scheduling for NR Multicast and Broadcast Services | OPPO |
| R1-2008375 | Considerations on MBMS group scheduling for RRC_CONNECTED UEs | Sony |
| R1-2008449 | Discussion on group scheduling mechanism for RRC_connected UEs | Apple |
| R1-2008826 | Mechanisms to Support Group Scheduling for RRC_CONNECTED UEs | ZTE |
| R1-2008833 | Discussion on mechanisms to support group scheduling for RRC_CONNECTED UEs | ETRI |
| R1-2008882 | Group Scheduling Mechanisms to Support 5G Multicast / Broadcast Services for RRC_CONNECTED UEs | Nokia, Nokia Shanghai Bell |
| R1-2008926 | Discussion on group scheduling mechanism for NR MBS | Lenovo, Motorola Mobility |
| R1-2008940 | Summary#1 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2008961 | Discussion on NR MBS group scheduling for RRC_CONNECTED UEs | MediaTek Inc. |
| R1-2009000 | Group Scheduling for NR-MBS | Intel Corporation |
| R1-2009055 | Discussion on mechanisms to support group scheduling for RRC_CONNECTED UEs | Asia Pacific Telecom co. Ltd |
| R1-2009163 | Mechanisms to support group scheduling for RRC_CONNECTED UEs | Convida Wireless |
| R1-2009165 | On group scheduling mechanism for NR multicast and broadcast | Convida Wireless |
| R1-2009238 | On Optimal Multiplexing for Simultaneous Operation of Broadcast/Multicast and Unicast Services | BBC |
| R1-2009274 | Views on group scheduling for Multicast RRC_CONNECTED UEs | Qualcomm Incorporated |
| R1-2009305 | Mechanisms to support group scheduling for RRC_CONNECTED Ues | Ericsson |
| R1-2009504 | Summary#2 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2009573 | Summary#3 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2009629 | Summary#4 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2009677 | Summary#5 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2009744 | Summary#6 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| 8.12.2 | Mechanisms to improve reliability for RRC_CONNECTED UEs | |
| R1-2007557 | Improving reliability for MC/BC services | FUTUREWEI |
| R1-2007563 | Mechanisms to improve reliablity for RRC_CONNECTED UEs | Huawei, HiSilicon |
| R1-2007638 | Study on the reliability for RRC_CONNNECTED UEs | CHENGDU TD TECH LTD. |
| R1-2007692 | Discussion on mechanisms to improve reliability for RRC_CONNECTED UEs | vivo |
| R1-2007836 | Discussion on reliability improvement mechanism for RRC_CONNECTED UEs in MBS | CATT |
| R1-2008035 | Discussion on reliability improvement | CMCC |
| R1-2008065 | Mechanisms to improve reliability of Broadcast/Multicast service | LG Electronics |
| R1-2008193 | On mechanisms to improve reliability for RRC_CONNECTED UEs | Samsung |
| R1-2008243 | UL feedback for RRC-CONNECTED UEs in MBMS | OPPO |
| R1-2008376 | Considerations on MBMS reliability for RRC_CONNECTED UEs | Sony |
| R1-2008450 | Discussion on MBS reliability improvement for RRC_connected UEs | Apple |
| R1-2008715 | Reliability improvement for RRC_CONNECTED UEs in MBS | Potevio |
| R1-2008827 | Mechanisms to Improve Reliability for RRC_CONNECTED UEs | ZTE |
| R1-2008883 | Reliability Improvements for RRC_CONNECTED UEs | Nokia, Nokia Shanghai Bell |
| R1-2008893 | Views on improving reliability for RRC_CONNECTED UEs in MBS | Google Inc. |
| R1-2008927 | Discussion on reliability improvement for RRC-CONNECTED UEs | Lenovo, Motorola Mobility |
| R1-2008962 | Discussion on HARQ operation for NR MBS reliable transmission | MediaTek Inc. |
| R1-2009001 | Mechanisms to Improve Reliability for NR-MBS | Intel Corporation |
| R1-2009164 | Mechanisms to improve reliability for RRC_CONNECTED UEs | Convida Wireless |
| R1-2009166 | On reliability enhancement for NR multicast and broadcast | Convida Wireless |
| R1-2009275 | Views on reliability enhancement for Multicast RRC_CONNECTED UEs | Qualcomm Incorporated |
| R1-2009306 | Discussion on reliability mechanisms for NR MBS | Ericsson |
| R1-2009464 | FL summary on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2009539 | FL summary#2 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2009654 | FL summary#3 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2009716 | FL summary#4 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| 8.12.3 | Basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | |
| R1-2007564 | Discussion on multicast support for IDLE/INACTIVE UEs | Huawei, HiSilicon |
| R1-2007639 | Basic functions for MBS for RRC_IDLE/RRC_INACTIVE UEs | CHENGDU TD TECH LTD. |
| R1-2007693 | Discussion on basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE Ues | vivo |
| R1-2007837 | Discussion on basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | CATT, CBN |
| R1-2008036 | Discussion on NR MBS in RRC_IDLE/RRC_INACTIVE states | CMCC |
| R1-2008066 | Basic function for broadcast/multicast | LG Electronics |
| R1-2008194 | On basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | Samsung |
| R1-2008244 | Discussion on enhancements for IDLE and INACTIVE state UEs | OPPO |
| R1-2008828 | Basic Functions for Broadcast or Multicast for RRC_IDLE or RRC_INACTIVE UEs | ZTE |
| R1-2008884 | Basic Functions for Broadcast / Multicast for RRC_IDLE / RRC_INACTIVE UEs | Nokia, Nokia Shanghai Bell |
| R1-2008928 | Basic functions for broadcast/multicast in idle/inactive states | Lenovo, Motorola Mobility |
| R1-2009002 | NR-MBS for RRC_IDLE/INACTIVE UEs | Intel Corporation |
| R1-2009167 | On NR multicast and broadcast for RRC_IDLE/RRC_INACTIVE UEs | Convida Wireless |
| R1-2009276 | Discussion on broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | Qualcomm Incorporated |
| R1-2009307 | Support for NR multicast reception in RRC Inactive/Idle | Ericsson |
| R1-2009465 | Feature lead summary on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/ RRC_INACTIVE states | Moderator (BBC) |
| R1-2009553 | Summary#2 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/ RRC_INACTIVE states | Moderator (BBC) |
| R1-2009554 | Summary#3 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/ RRC_INACTIVE states | Moderator (BBC) |
| 8.12.4 | Other | |
| R1-2007641 | Effects of NR MBS on PDSCH and PDCCH | CHENGDU TD TECH LTD. |
| R1-2007694 | Other issues for Rel-17 MBS | vivo |
| R1-2007838 | Discussion on search space type definition for group scheduling | CATT |
| R1-2008067 | Other aspects for MBS | LG Electronics |
| R1-2008245 | PUCCH resource allocation for UL feedback in MBMS | OPPO |
| R1-2008317 | Resource for receiving MBS | Huawei, HiSilicon |
| R1-2008829 | Preliminary Simulation Results of Rel-17 MBS | ZTE |
| R1-2009308 | Assumptions for Performance Evaluations of NR-MBS | Ericsson |
| 8.13 | NR Dynamic spectrum sharing (DSS) | |
| R1-2009205 | Work plan for Rel17 WI on NR Dynamic spectrum sharing (DSS) | Ericsson |
| 8.13.1 | Cross-carrier scheduling (from Scell to Pcell) | |
| R1-2007579 | Discussion on SCell PDCCH scheduling P(S)Cell PDSCH or PUSCH | Huawei, HiSilicon |
| R1-2007695 | Discussion on Scell scheduling Pcell | vivo |
| R1-2007839 | Disucssion on cross-carrier scheduling from Scell to Pcell | CATT |
| R1-2008062 | Discussion on cross-carrier scheduling from SCell to Pcell | LG Electronics |
| R1-2008110 | Discussion on cross-carrier scheduling from SCell to Pcell | Spreadtrum Communications |
| R1-2008195 | Cross carrier scheduling from SCell to Pcell | Samsung |
| R1-2008284 | Discussion on cross-carrier scheduling from Scell to Pcell | OPPO |
| R1-2008451 | Views on Rel-17 DSS SCell scheduling PCell | Apple |
| R1-2008695 | Discussion on cross-carrier scheduling from SCell to PCell | ASUSTeK |
| R1-2008830 | Discussion on Cross-Carrier Scheduling from SCell to PCell | ZTE |
| R1-2009003 | On SCell scheduling PCell transmissions | Intel Corporation |
| R1-2009023 | Cross-carrier scheduling from SCell to Pcell | ETRI |
| R1-2009040 | Discussion on Cross-carrier scheduling from SCell to Pcell | Xiaomi |
| R1-2009046 | Cross-carrier scheduling from SCell to Pcell | Nokia, Nokia Shanghai Bell |
| R1-2009085 | Search space monitoring to support SCell scheduling PCell | InterDigital, Inc. |
| R1-2009110 | Cross-carrier scheduling (from Scell to Pcell) | Lenovo, Motorola Mobility |
| R1-2009195 | Discussion on cross-carrier scheduling enhancements for NR DSS | NTT DOCOMO, INC. |
| R1-2009206 | Enhanced cross-carrier scheduling for DSS | Ericsson |
| R1-2009277 | Views on cross-carrier scheduling from an SCell to the PCell/PSCell | Qualcomm Incorporated |
| R1-2009486 | Summary of Email discussion [103-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2009806 | Summary#2 of Email discussion [103-e-NR-DSS-01] | Moderator (Ericsson) |
| 8.13.2 | Multi-cell PDSCH scheduling via a single DCI | |
| R1-2007580 | Discussion on multi-carrier scheduling using single PDCCH | Huawei, HiSilicon |
| R1-2007696 | Discussion on joint scheduling | vivo |
| R1-2007840 | Discussion on multi-cell PDSCH scheduling via a single DCI | CATT |
| R1-2008063 | Discussion on multi-cell PDSCH scheduling via a single DCI | LG Electronics |
| R1-2008111 | Discussion on multi-cell PDSCH scheduling via a single DCI | Spreadtrum Communications |
| R1-2008196 | On the use of one DCI format for scheduling on two cells | Samsung |
| R1-2008285 | Discussion on multi-cell PDSCH scheduling via a single DCI | OPPO |
| R1-2008452 | Views on Rel-17 DSS Multi-cell PDSCH scheduling via a single DCI | Apple |
| R1-2008696 | Discussion on multi-cell PDSCH scheduling via a single DCI | ASUSTeK |
| R1-2008831 | Discussion on Multi-cell PDSCH Scheduling via a Single DCI | ZTE |
| R1-2008835 | Multi-cell scheduling and dormancy | Charter Communications |
| R1-2008929 | Discussion on multi-cell PDSCH scheduling via a single DCI | Lenovo, Motorola Mobility |
| R1-2008963 | Evaluation on On Multi-cell PDSCH Scheduling via Single DCI | MediaTek Inc. |
| R1-2009004 | On 2-cell scheduling via single DCI | Intel Corporation |
| R1-2009024 | Discussion on multi-cell PDSCH scheduling via a single DCI | ETRI |
| R1-2009047 | On support of Single DCI scheduling two cells | Nokia, Nokia Shanghai Bell |
| R1-2009086 | Discussion on the support of single DCI scheduling multi-cell | InterDigital, Inc. |
| R1-2009196 | Discussion on multi-cell PDSCH scheduling via a single DCI for NR DSS | NTT DOCOMO, INC. |
| R1-2009207 | Study on single DCI scheduling PDSCH on multiple cells | Ericsson |
| R1-2009278 | Views on multi-cell PDSCH scheduling via a single DCI | Qualcomm Incorporated |
| R1-2009559 | Feature lead summary#1 on multi-cell scheduling via a single DCI | Moderator (Lenovo) |
| R1-2009815 | Final Feature lead summary on multi-cell scheduling via a single DCI | Moderator (Lenovo) |
| 8.13.3 | Support efficient activation/de-activation mechanism for SCells in NR CA | |
| R1-2007548 | Support efficient activation/de-activation mechanism for Scells | FUTUREWEI |
| R1-2007697 | Discussion on efficient activation/de-activation mechanism for Scells | vivo |
| R1-2007841 | Disucssion on efficient activation/de-activation mechanism for Scell in NR CA | CATT |
| R1-2008112 | Discussion on efficient activationde-activation mechanism for SCells in NR CA | Spreadtrum Communications |
| R1-2008197 | On efficient activation/de-activation mechanism for Scells | Samsung |
| R1-2008286 | Discussion on efficient activation/de-activation for Scell | OPPO |
| R1-2008322 | Discussion on efficient activation/de-activation mechanism for SCells | Huawei, HiSilicon |
| R1-2008453 | On efficient SCell Activation/Deactivation | Apple |
| R1-2008713 | Efficient activation/deactivation of SCell | ASUSTeK |
| R1-2008832 | Discussion on Support Efficient Activation De-activation Mechanism for SCells in NR CA | ZTE |
| R1-2008849 | Discussion on efficient activation mechanism for SCells | NEC |
| R1-2008968 | On supporting efficient activation mechanism for SCells in NR CA | MediaTek Inc. |
| R1-2009005 | On efficient activation/de-activation for SCells | Intel Corporation |
| R1-2009048 | On low latency Scell activation | Nokia, Nokia Shanghai Bell |
| R1-2009197 | Discussion on efficient activation/deactivation mechanism for SCells | NTT DOCOMO, INC. |
| R1-2009208 | Reduced Latency SCell Activation | Ericsson |
| R1-2009279 | Views on efficient activation/de-activation mechanism for SCells in NR CA | Qualcomm Incorporated |
| R1-2009569 | Summary#1 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2009666 | Summary#2 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2009712 | Summary#3 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2009786 | [Draft] LS on temporary RS for efficient SCell activation in NR CA | Huawei |
| R1-2009798 | LS on temporary RS for efficient SCell activation in NR CA | RAN1, Huawei |
| R1-2009800 | Final Summary of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| 8.14 | Study on XR Evaluations for NR (RAN1) | |
| R1-2009283 | On work plan for SI on XR Evaluations for NR | Qualcomm Incorporated |
| 8.14.1 | Applications, Traffic Model and Evaluation Methodology | |
| R1-2007555 | XR applications and scenarios | FUTUREWEI |
| R1-2007561 | Discussion on applications, traffic model, and evaluation methodology for XR and Cloud Gaming | Huawei, HiSilicon |
| R1-2007698 | Discussion on XR applications, traffic model and evaluation methodologies | vivo |
| R1-2007843 | XR use cases, evaluation methodologies and traffic model | CATT |
| R1-2007976 | Discussion on applications, traffic model and evaluation methodology for XR | ZTE |
| R1-2008037 | Discussion on XR evaluation and Challenges for NR | CMCC |
| R1-2008198 | Applications, Evaluation Methodology, and KPIs for XR | Samsung |
| R1-2008311 | XR evaluations for NR: Applications and Evaluation Methodology | AT&T |
| R1-2008454 | XR Applications, Traffic Model and Evaluation Methodology | Apple |
| R1-2008818 | Discussion on traffic models and evaluation assumptions for XR | InterDigital, Inc. |
| R1-2008896 | Applications, Traffic Model and Evaluation Methodology for XR evaluations for NR | Nokia, Nokia Shanghai Bell |
| R1-2008939 | Discussion for study in XR evaluation for NR | LG Electronics |
| R1-2008967 | On Applications, Traffic Model, and Evaluation Methodology for XR and CG | MediaTek Inc. |
| R1-2009006 | Scenarios, Traffic Model and EVM for XR | Intel Corporation |
| R1-2009041 | Discussion on XR application and evaluation methodology | Xiaomi |
| R1-2009087 | XR use cases, traffic modelling and performance measure | Ericsson |
| R1-2009198 | Discussion on study on XR evaluations for NR | NTT DOCOMO, INC. |
| R1-2009280 | Evaluation Methodology for XR | Qualcomm Incorporated |
| R1-2009812 | FL Summary of RAN1 103-e agreements and email discussions on Rel-17 SI on XR evaluations for NR | Moderators (Qualcomm, vivo) |
| 8.14.2 | Other | |
| R1-2007699 | Performance evaluation of XR traffic | vivo |
| R1-2007842 | Potential area of NR enhancement for the support of XR services | CATT |
| R1-2008316 | Initial evaluation results for XR and Cloud Gaming | Huawei, HiSilicon |
| R1-2008455 | Views on enhancements for XR | Apple |
| R1-2008819 | Discussion on potential enhancements for XR | InterDigital, Inc. |
| R1-2009281 | TR skeleton for Study on XR Evaluations for NR | Qualcomm Incorporated |
| R1-2009289 | Initial XR performance evaluations | Ericsson |
| R1-2009707 | TR38.838 Skeleton for Study on XR (Extended Reality) evaluations for NR | Rapporteur (Qualcomm) |
| R1-2009811 | TR38.838 Skeleton for Study on XR (Extended Reality) evaluations for NR | Rapporteur (Qualcomm) |
| R1-2009818 | TR38.838 Skeleton for Study on XR (Extended Reality) evaluations for NR | Rapporteur (Qualcomm) |
| 8.15 | Study on NB-IoT/eMTC support for Non-Terrestrial Network | |
| R1-2007882 | NB-IoT Waveform Tests over LEO Satellite | OQ Technology |
| R1-2009096 | Rel-17 IoT NTN Work Plan | MediaTek Inc., Eutelsat |
| R1-2009838 | Session notes for 8.15 (Study on NB-IoT/eMTC support for Non-Terrestrial Network) | Ad-Hoc Chair (Ericsson) |
| 8.15.1 | Scenarios applicable to NB-IoT/eMTC | |
| R1-2007572 | Application scenarios of IoT in NTN | Huawei, HiSilicon |
| R1-2007844 | Application scenarios discussion on NB-IoT/eMTC | CATT |
| R1-2008038 | Discussion on scenarios for IoT NTN | CMCC |
| R1-2008199 | On Scenarios applicable to NB-IoT/eMTC | Samsung |
| R1-2008257 | Discussion on scenarios applicable to NB-IoT/eMTC | OPPO |
| R1-2008815 | Reference Link-Budget parameters for IoT NTN | Eutelsat S.A. |
| R1-2008854 | Preliminary views on the scenarios and assumption for IoT-NTN | ZTE |
| R1-2008868 | Email summary discussion on Scenarios applicable to NB-IoT/eMTC | Eutelsat S.A. |
| R1-2009007 | On scenarios for NB-IoT and eMTC NTN | Intel Corporation |
| R1-2009042 | Discussion on the scenarios for NB-IoT/eMTC over NTN | Xiaomi |
| R1-2009088 | On scenarios and evaluations for eMTC and NB-IoT based NTN | Ericsson |
| R1-2009098 | Discussion on scenarios applicable to NB-IoT over NTN | Sateliot |
| R1-2009114 | Scenarios applicable to NB-IoT/eMTC | Qualcomm Incorporated |
| R1-2009215 | Observations on NB-IoT/eMTC for NTN scenarios | Nokia, Nokia Shanghai Bell |
| R1-2009235 | Scenarios for support of NB-IoT and eMTC over NTN | Sony |
| R1-2009304 | Discussion on IoT NTN scenarios - link budget | MediaTek Inc., Eutelsat |
| 8.15.2 | Necessary changes to support NB-IoT and eMTC over satellite | |
| R1-2007573 | Solutions to support IoT in NTN | Huawei, HiSilicon |
| R1-2007845 | Potential enhancements to support NB-IoT and eMTC over satellite | CATT |
| R1-2008039 | Discussion on enhancements for IoT NTN | CMCC |
| R1-2008200 | On Necessary changes to support NB-IoT and eMTC over satellite | Samsung |
| R1-2008258 | Discussion on necessary changes to support NB-IoT/eMTC over NTN | OPPO |
| R1-2008456 | Potential Enhancement for NB-IoT/eMTC over Satellite | Apple |
| R1-2008855 | Discussion on enhancements for IoT-NTN | ZTE |
| R1-2008921 | Enhancement to Support NBIoT and eMTC on NTN | Lenovo, Motorola Mobility |
| R1-2009008 | On enhancements for NB-IoT and eMTC NTN | Intel Corporation |
| R1-2009043 | Necessary changes to support NB-IoT and eMTC over satellite | Xiaomi |
| R1-2009089 | An overview of technical aspects in IoT NTN | Ericsson |
| R1-2009095 | Discussion on RAN1 Aspects of IoT NTN | MediaTek Inc., Eutelsat |
| R1-2009115 | Necessary changes to support NB-IoT and eMTC over satellite | Qualcomm Incorporated |
| R1-2009199 | On necessary changes to support IoT devices in NTN | InterDigital, Inc. |
| R1-2009216 | Necessary changes to support NB-IoT and eMTC over satellite | Nokia, Nokia Shanghai Bell |
| R1-2009236 | Considerations for support of NB-IoT and eMTC over NTN | Sony |
| 8.15.3 | Other | |
| R1-2008259 | Discussion on other aspects | OPPO |
| R1-2008320 | Other aspects to support IoT in NTN | Huawei, HiSilicon |
| R1-2008856 | Discussion on power consumption and NPRACH capacity for NTN | ZTE |
| R1-2009090 | On evaluation assumptions for eMTC and NB-IoT based NTN | Ericsson |
| 8.16 | Introduction of DL 1024QAM for NR FR1 | |
| R1-2007617 | On support of DL 1024QAM for NR FR1 | Huawei, HiSilicon |
| R1-2007700 | On supporting DL 1024QAM for NR FR1 | vivo |
| R1-2007846 | DL 1024QAM for NR FR1 | CATT |
| R1-2007977 | Discussion on DL 1024QAM for NR FR1 | ZTE |
| R1-2008201 | Discussion on DL 1024QAM for NR FR1 | Samsung |
| R1-2009009 | Support of 1024QAM | Intel Corporation |
| R1-2009171 | Work plan on supporting 1024 QAM | Rapporteurs (Nokia, Ericsson) |
| R1-2009172 | Considerations for NR DL 1024 QAM in FR1 | Nokia, Nokia Shanghai Bell |
| R1-2009209 | 1024QAM for NR DL | Ericsson |
| R1-2009282 | Introduction of 1024-QAM modulation for NR PDSCH | Qualcomm Incorporated |
| R1-2009799 | Summary of Email discussion [103-e-NR-1024QAM-01] | Moderator (Ericsson) |